As of now, to authenticate with a git repository you are required to provide SSH or basic auth permissions. These tend to be long lived in nature and some users are interested in more just in time credentials such as managed identities in Azure.
This piece of work would depend on users providing the Kratix pod access to an identity with permissions to read/write to the ADO repo, and from there Kratix would manage generating a token and authenticating all actions using that identity.
Similar work was done to support S3 Buckets via AWS IAM permissions here.
As of now, to authenticate with a git repository you are required to provide SSH or basic auth permissions. These tend to be long lived in nature and some users are interested in more just in time credentials such as managed identities in Azure.
This piece of work would depend on users providing the Kratix pod access to an identity with permissions to read/write to the ADO repo, and from there Kratix would manage generating a token and authenticating all actions using that identity.
Similar work was done to support S3 Buckets via AWS IAM permissions here.