Add 'password' input type for manual workflows #12764
Replies: 49 comments 7 replies
-
|
Appreciate the feedback @TaffarelJr - this is good feedback. There are some details that we'll definitely want to think through because - as you note - these are your secrets. 😁 But your use case makes sense. Thanks again for the feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Has there been any updates for this? I am interested in this as well. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ethomson Any updates on Adding |
Beta Was this translation helpful? Give feedback.
-
|
I could be wrong, but I think it's more secure keeping some secrets on my offline password manager. That's why I would rather type passwords each time I need to manually trigger a workflow. |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
This is just what I need, a password input type. |
Beta Was this translation helpful? Give feedback.
-
|
This is exactly what I am looking for |
Beta Was this translation helpful? Give feedback.
-
|
I would love that |
Beta Was this translation helpful? Give feedback.
-
|
Over a year... and nothing new? I do confirm that it is simply not possible to use Azure (non) secrets (at all) in certain cases. (e.g. echo from some base 64...) So please add another string type such as masked, password, secret, whatever you like, as long as it has a masking effect when you enter it. |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
While the comments might help, you might also want to upvote the author's post so it gets more attention. |
Beta Was this translation helpful? Give feedback.
-
|
I really want this e.g. ## To avoid expression render ${{ }} and retrieve the value
export SPOTINST_TOKEN=$(jq -r '.inputs.SPOTINST_TOKEN' ${GITHUB_EVENT_PATH})
## Add mask to hide if necessary
echo "::add-mask::${SPOTINST_TOKEN}"Just read the input directly from the event file that is placed on each run. This way, we don't need to render the Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, I wrote a small ViolentMonkey script. It is activated via Shift after the page is loaded :). |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
-
|
almost 3 years, still no update? |
Beta Was this translation helpful? Give feedback.
-
|
This would be very valuable for my initialization pipeline |
Beta Was this translation helpful? Give feedback.
-
|
At least 2 legit use cases and 3 years since the initial request. |
Beta Was this translation helpful? Give feedback.
-
|
We use GitHub workflows for cloud deployments. A password is required to run those workflows. We use the scripts below to avoid having the password printed in logs. Sure would appreciate a "password" input type. Or RBAC for workflows. DEPLOY_PASSWORD=$(cat $GITHUB_EVENT_PATH | jq -r '.inputs.DEPLOY_PASSWORD')
echo "::add-mask::${DEPLOY_PASSWORD}"AWK incantations when DEPLOY_PASSWORD=$(cat $GITHUB_EVENT_PATH | sed 's/[{}]/ /g' | awk -v k="DEPLOY_PASSWORD" '{for(i=1; i<=NF; i++) {if ($i ~ k) {print $(i+1)}}}' | sed -e 's/[",]*//g')
echo "::add-mask::${DEPLOY_PASSWORD}" |
Beta Was this translation helpful? Give feedback.
-
|
My legit use case on this is as a second line of security. I want to be able to trigger databae restores from actions. But I want to store like a restore password as a secret, and then I can check the input against the secret before triggering a restore. Unless I can somehow limit the trigger dispatch to my user only but still allow other users with the right github pers to execute other workflows. |
Beta Was this translation helpful? Give feedback.
-
|
Ping |
Beta Was this translation helpful? Give feedback.
-
|
bumpy |
Beta Was this translation helpful? Give feedback.
-
|
bump |
Beta Was this translation helpful? Give feedback.
-
|
Bump! |
Beta Was this translation helpful? Give feedback.
-
|
There are work-arounds/hacks but this is such an obvious use case.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
The input types for manual workflows are great so far:
stringchoicebooleanenvironmentBut I could really use a
passwordinput type.I need to deploy infrastructure-as-code from my GitHub Action, and I need to be able to prompt for Admin credentials from whoever is running the workflow. I bet I could make it work with a plain
string, but I have a feeling my password shouldn't be floating across the internet unprotected. At the very least, a masking effect would be nice to prevent the password from being seen on the screen.Beta Was this translation helpful? Give feedback.
All reactions