You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
I'd like for the operator to allow GitHubAppCredentials type credentials to configure the git SCM for seed jobs. This is already supported in the git SCM, i suppose because GitHubAppCredentials implements StandardUsernamePasswordCredentials ..but i'm not sure. I know i can update the credentials on the operator-created seed job ( with no other changes ) and scan and checkout will both work.
Describe alternatives you've considered
Moving away from personal access tokens to github apps, there isn't an alternative it seems: I currently configure the seed job with an app client secret ( username + password ) that validates in the operator but fails to authenticate at scan-time. I log in to the UI, update the seed job credential to the GitHubAppCredentials one ( appid + private key ) and everything works.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this issue is still affecting you, just comment with any updates and we'll keep it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!
Describe the solution you'd like
I'd like for the operator to allow
GitHubAppCredentials
type credentials to configure the git SCM for seed jobs. This is already supported in the git SCM, i suppose becauseGitHubAppCredentials
implementsStandardUsernamePasswordCredentials
..but i'm not sure. I know i can update the credentials on the operator-created seed job ( with no other changes ) and scan and checkout will both work.Describe alternatives you've considered
Moving away from personal access tokens to github apps, there isn't an alternative it seems: I currently configure the seed job with an app client secret ( username + password ) that validates in the operator but fails to authenticate at scan-time. I log in to the UI, update the seed job credential to the
GitHubAppCredentials
one ( appid + private key ) and everything works.The text was updated successfully, but these errors were encountered: