-
Notifications
You must be signed in to change notification settings - Fork 33
Shellck5 #799
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
Merged
Merged
Shellck5 #799
Changes from 13 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
572b6b8
Housekeeping: lint remaining scripts in bin
gsmith-sas 0159263
Remove obsolete references to Elasticsearch and Kibana
gsmith-sas 3e88c87
Housekeeping: lint remaining scripts in bin
gsmith-sas 5093fab
Linting (round 2)
gsmith-sas e5bef8e
Linting (round 3)
gsmith-sas c9ce361
Linting (shellck)
gsmith-sas 922df21
Linting (final nits?)
gsmith-sas ef4d0d0
Correct typo: AlertManager
gsmith-sas f506527
[FIX] Corrects args sequence in tls_cert_managed_by_v4m
gsmith-sas fee54dd
Remove SC2269s
gsmith-sas dd41e95
Moved SC2148 disable comments
gsmith-sas 261f40a
Removed an occurance of SC2034
gsmith-sas bbf25eb
Removed obsolete airgap temp dir
gsmith-sas a3eed25
Fix quoting issue in ocVersionCheck
gsmith-sas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just curious what this change is here? Do we not actually need these lines?
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.
We originally had lines assigning these variables the values already assigned to them (e.g. SMTP_HOST="${SMTP_HOST}"). Why? Mostly they were artifacts of the early implementation work, as we sorted out what parameters were needed..but the lines also clarified what inputs this functionality required or used. When shellck flagged them, I thought the latter reason was still valid and added the
shellcheck disable
comments. But, later when looking over things one more time, I decided that keeping the line AND adding the disabling quotes was silly and the documentation objective could be achieved more cleanly with comments. Which is what we ended up with. I don't like the idea of code responding to apparently random environment variables. Documenting which environment variables are intended to influence behavior seems "better".