-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
In case the secret should be stored as a username and password, the username should be specified in a secret label but if the username contains the @ sign it isn't allowed in the gcp secret manager label.
Today usernames in the email format are very common so that limitation is the blocker,
Suggestion : store the username as the secret annotation instead of the label.
[JENKINS-73491] GCP secret manager doesn't allow special characters in labels
Comment |
[ Hello,
Thanks for sharing this info. Its really very helpful to us. [choiceadvantage|https://www-choiceadvantage.com] Best regards, samuel898 ] |
Comment |
[ Google Cloud Secret Manager has specific requirements for labels, which might be why you’re encountering issues with special characters ! [https://www.vanilla-giftcardbalance.com|https://www.vanilla-giftcardbalance.com/]
] |
markewaite I know
that's exactly the problem.
Todays we have many systems which expect to accept the user name in the email format (with @) . So I can't use the GCP secret manager for storing credentials for these systems so Jenkins will be using them in its jobs.
Today I must store these credentials in other stores ( for example in the jenkins internal store) just because I can't write the user name with @ in the gcp secret label