-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Region is getting masked #368
Comments
Got my solution if we don't want your aws region to get masked please don't use it as a secret like {{secrets.AWS_REGION}} simply hard code it in our workflow commands. |
|
I am not using it as a secret. But instead of hard coding it, I use a variable. But still it is masked. |
This action doesn't set the region as a secret in code like it does with the keys. Can you please share reproduction steps i.e. your workflow file @vesubramanian? |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
PFB. I am not at all using region as a secret, but reading from the matrix. But still it is masked in the output. You can try this. When I reached out to the support, they were also able to reproduce this and they said, they have communicated this to the engineering team, who were also able to reproduce this. But they haven't given an ETA for the fix.
|
I wasn't able to reproduce this @vesubramanian,
This is interesting to me, I'm not sure which team they reached out to. Do you have any sort of reference to this support issue so I can try to look it up? |
Please feel free to ping me if this issue persists and you have more info on how I can reproduce it. Thanks |
|
On using this action, the region is also getting masked.
The text was updated successfully, but these errors were encountered: