[JIRA] (JENKINS-60693) Allow editing credential id

[rittneje@gmail.com (JIRA)]

Jesse Rittner created an issue

Jenkins / JENKINS-60693 Allow editing credential id Issue Type: Story Assignee: Unassigned Components: credentials-plugin Created: 2020-01-08 13:28 Priority: Minor Reporter: Jesse Rittner Currently there appears to be no way to change the id of a credential once it has been created. The user instead is required to manually create a new secret with the same contents. This is very annoying, especially because it requires tracking down the actual credentials themselves again. Instead, the credential id should be a mutable property of a credential. It would also be acceptable if there were simply an option to clone a credential with a new id. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-60693

Re: Allow editing credential id Note that Credential IDs are stored as strings in objects which use these credentials. Although changing IDs could be a useful feature, tracking down and renaming credentials usages would be a pain. Examples:external usages in Configuration as Code and Pipeline scripts/libraries . I doubt it can be automated if there is such expectation in this ticket

Add Comment

[rittneje@gmail.com (JIRA)]

Jesse Rittner commented on JENKINS-60693

Re: Allow editing credential id

Oleg Nenashev If you mean that I would still have to manually update the credential id at each use site (e.g., withCredentials in a Jenkinsfile), that is perfectly acceptable. This is just to be able to fix poorly or improperly named secrets without having to track them down out-of-band, or circumvent the redaction and print them to the logs. Like I said, it would be okay if there were simply a way to clone an existing credential using a new credential id. Then I could just delete the original version myself, and the end result is the same as far as I need.

Add Comment