-
Improvement
-
Resolution: Unresolved
-
Minor
-
credentials-2.3.0
Hi there, since JENKINS-58170 there's a new checkbox - "List user credentials" in the credentials parameter, that's by default unchecked. When checked, the user-scoped secrets can be selected from the drop-down.
This changed the previous behavior which had no checkbox and the drop-down contained the user-scoped creds by default.
Although I think I understand the reasoning behind why it was added, I don't think all users need to explicitly consent twice that they want to select a user-scoped credential.
My whole team uses these parameters as a workaround to JENKINS-44772 several times a day and we all would be thrilled for a fix. As I know there's quite some hesitance to fix it at all, we'll be grateful for at least some old-days compatible UX:
- One approach could be to add a config option for the default state of the user-scoped checkbox in the configuration/pipeline script (along these lines).
- Another option could be to allow selecting user-scoped credentials by default as before, but display the warning when a user-scoped credential gets selected.
Both options are IMHO quite easy to implement and they would give users more control while retaining the new safety measures where desired.
FYI:
jvz, as author of the latest change you might want to put in your 2¢.
stephenconnolly (I know you’re very busy) since you have a vision for how user credentials work you may be interested too.
Apologies for not explaining why I was tagging you originally in this comment.