You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Variables were recently allowed to be set in manual pipeline runs.
The article says that secure variables manually set in the pipeline will not be hidden. Is there an initiative to allow the hiding of variables in manually run pipelines?
As you already know this is not an available feature. The only option I see for you regarding credentials is temporarily updating them in the Bitbucket Repository configuration >> Repository variables before running the manual build.
I've opened an improvement request for this in order to track interest in this feature:
Please let me know If I can still be of any help on this topic.
Where is this? We have run into this issue and makes us question the viability of Atlassian Bitbucket as a robust CI/CD tool as it is exposing secure credentials for our production environments. Please advise on masking input variables over top the repository variables. Manually change the repo variables for builds is not a good solution.
I also don't see the verbiage stating manually set variables in the pipeline will not be masked. In fact the docs states: "Pipelines masks all occurrences of a secure variable's value in your log files, regardless of how that output was generated."
"If you have secure variable value set to a common word, that word will be replaced with the variable name anywhere it appears in the log file."