-
Bug
-
Resolution: Unresolved
-
Minor
-
None
When having a secret in two different projects (e.g. dev environment, production environment), specifying the two projects discovers both secrets, but because the secret name is used as the credential id in Jenkins the one read later overrides the earlier.
To fix, maybe we can add the project name to the credential id.