-
New Feature
-
Resolution: Unresolved
-
Major
-
None
We have som credentials contain underscore in an existing Jenkins instance. This prevents us from migrating old credentials to this new format.
We hope there's a way to customize the credentials name containing the string not allowed by Kubernetes.
NOTE PRs to address this in kubernetes-credentials-provider will not be accepted. see this comment as to why. The ticket is still open as this can be done completely outside of the kubernetes-credentials-provider plugin
- is related to
-
JENKINS-57328 Should not use secret name as credential ID
-
- Open
-
Running into the same issue:
Maybe we could add a label of `"jenkins.io/credentials-id": "SOME_UNDERSCORED_NAME"` to be used as the credential ID rather than `metadata.name`?