-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Warn about newlines in secrets (3.18) #198
Conversation
I am a bot, here are the test results for this PR:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks fine, but the whole script might be better off rewritten at some point if we keep needing to nest more conditionals and loops like this.
Actually that's a good point, I hadn't noticed that since I made the changes to standardise this over all the bases during the s6v3 migration that there's a redundant if in there, fixed in 7c6601c |
And then actually fixed in 1b98fd9 |
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
I think most of it could be made into a function and then just the top line find command could exec the function. with that |
No, we're confirming that the file that the FILE__ env points to exists, it's not a redundant check. |
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
Description:
This is an attempt to deal with the dozens of people who create secrets with errant newlines. By default it will remove any newline characters from secrets before assigning to them envs. There is an undocumented bypass for the 3 people who will inevitably have some horrible edge case where they're legitimately using multi-line envs in secrets.
Benefits of this PR and context:
How Has This Been Tested?
Source / References: