Git

use the git integration to connect resolve ai to your codebase to query code during investigations, pull relevant evidence, and propose code changes for you to review there are two ways to give resolve ai access to your code docid\ xiugahvmkosyftgtp 0zp docid 3dsocdqk0zscfogpvspho (kubernetes or docid 6skdvmwgbcng2ierfbv8h ) cloud vs satellite area git on cloud git on satellite (kubernetes) git on satellite (ecs) where git commands run resolve managed cloud infrastructure your satellite in your kubernetes cluster your satellite on aws ecs fargate who operates infrastructure resolve your team your team repository reachability requirement reachable from resolve cloud reachable from satellite network reachable from satellite vpc storage location resolve managed persistent storage gitvolume on satellite ( emptydir or pvc) efs volume on satellite best fit fast onboarding, no cluster work private networks, compliance, data residency aws native, no kubernetes required auth and write behavior these behaviors apply to both cloud and satellite auth config is defined under authconfigs token auth additionally requires matching keys in tokenauthcredentials write tools are controlled by disablewrites true read only (write tools blocked) false write tools available if disablewrites is omitted default is writes enabled if any auth config is type "github" default is read only if auth configs are token only next steps for resolve managed execution docid\ xiugahvmkosyftgtp 0zp for in cluster execution docid 3dsocdqk0zscfogpvspho for aws ecs execution docid 6skdvmwgbcng2ierfbv8h any questions? contact us at mailto\ help\@resolve ai