-
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
-
[JENKINS-62360] Ability to customize credentials id
Yi Gong
created issue -
| Assignee | Original: James Nord [ teilo ] |
Gareth Evans
made changes -
| Assignee | New: Gareth Evans [ garethjevans ] |
| Summary | Original: Ability to customize credentials name | New: Ability to customize credentials id |
| Link | New: This issue is related to JENKINS-57328 [ JENKINS-57328 ] |
| Assignee | Original: Gareth Evans [ garethjevans ] | New: James Nord [ teilo ] |
| Assignee | Original: James Nord [ teilo ] |
| Description |
Original:
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. |
New:
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 the comment as to why |
| Description |
Original:
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 the comment as to why |
New:
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|https://issues.jenkins.io/browse/JENKINS-62360?focusedCommentId=426652&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-426652] as to why. The ticket is still open as this can be done completely outside of the kubernetes-credentials-provider plugin |