Replies: 3 comments 2 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Hi, Good idea, and it fits a real gap. Here is how this works today and what you can do in the meantime. Why it matters (as far as I know)
Workaround 1 (for A reusable workflow can declare secrets, and the caller passes them. These are masked automatically: # reusable workflow
on:
workflow_call:
secrets:
new_password:
required: true
jobs:
run:
runs-on: ubuntu-latest
steps:
- run: ./rotate.sh
env:
NEW_PASSWORD: ${{ secrets.new_password }}# caller
jobs:
call:
uses: ./.github/workflows/reusable.yml
secrets:
new_password: ${{ secrets.SOME_SECRET }}The limitation: a secret must come from a stored secret (or an earlier step's output that was masked), so it doesn't cover a value typed in by a person at run time. Workaround 2: mask the input yourself, as the first step steps:
- name: Mask input
run: echo "::add-mask::${{ inputs.new_password }}"Be careful with this one:
- name: Mask input
env:
VALUE: ${{ inputs.new_password }}
run: echo "::add-mask::$VALUE"
Workaround 3: don't pass the value as an input
For compliance (SOC 2, PCI) Auditors usually care that secrets are never stored in plain text or in logs. Because inputs are kept with the run, I'd treat them as non-secret for audit purposes and use secrets or an external secrets manager for anything sensitive. On the proposal Your idea is clear, and a field that both masks the value in logs and excludes it from the stored payload and UI would be valuable. Two points worth adding to the feedback: the key name should be spelled |
|
3 Useful Websites You Shouldn't Miss! AgeWise: https://agewise-life-lens.lovable.app/ ReelSave: https://reelsave-guide.hatchable.site/ Calculator Hub: https://calculator-net-hub.netlify.app/ |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Actions Runner
Discussion Details
The idea is a simple one:
once an input is marked as sensetive/secret/must-be-masked. its value is immediately masked in all logs.
The idea is to help creating workflows that can handle secrets and allow being SOC2 and PCI compliance processes to be built in github actions.
All reactions