Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Postponed
-
None
Description
When the custom clients feature is enabled, credentials use the secret ARN as their ID rather than the secret name.
However when a job attempts to bind a credential that uses the secret ARN as its ID, the binding fails with an error along the lines of "could not find credential with the ID '<ARN>'".
The same binding for the same credential works fine when the default client is used, so the credential uses the secret name instead.
In the absence of general namespacing capabilities for credentials, ARNs are the only mechanism available to us to let secrets from multiple accounts (potentially with the same name) coexist with each other. If credentials aren't able to bind using ARNs then this will put the brakes on multi-account support (
JENKINS-63183,JENKINS-63184,JENKINS-59670and others), and we'll have to remove that beta feature.