-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Clean up relay credentials generation #1289
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
Changes from all commits
Commits
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| echo "${_group}Ensuring Relay credentials ..." | ||
|
|
||
| RELAY_CONFIG_YML="../relay/config.yml" | ||
| RELAY_CREDENTIALS_JSON="../relay/credentials.json" | ||
|
|
||
| ensure_file_from_example $RELAY_CONFIG_YML | ||
|
|
||
| if [[ -f "$RELAY_CREDENTIALS_JSON" ]]; then | ||
| echo "$RELAY_CREDENTIALS_JSON already exists, skipped creation." | ||
| else | ||
|
|
||
| # There are a couple gotchas here: | ||
| # | ||
| # 1. We need to use a tmp file because if we redirect output directly to | ||
| # credentials.json, then the shell will create an empty file that relay | ||
| # will then try to read from (regardless of options such as --stdout or | ||
| # --overwrite) and fail because it is empty. | ||
| # | ||
| # 2. We need to use -T to avoid additional garbage output cluttering | ||
| # credentials.json under Docker Compose 1.x and 2.2.3+. Note that the | ||
| # long opt --no-tty doesn't exist in Docker Compose 1. | ||
|
|
||
| creds="$dcr --no-deps -T relay credentials" | ||
| $creds generate --stdout > "$RELAY_CREDENTIALS_JSON".tmp | ||
| mv "$RELAY_CREDENTIALS_JSON".tmp "$RELAY_CREDENTIALS_JSON" | ||
| if ! grep -q Credentials <($creds show); then | ||
| # Let's fail early if creds failed, to make debugging easier. | ||
| echo "Failed to create relay credentials in $RELAY_CREDENTIALS_JSON." | ||
| exit 1 | ||
| fi | ||
| echo "Relay credentials written to $RELAY_CREDENTIALS_JSON." | ||
| fi | ||
|
|
||
| echo "${_endgroup}" | ||
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.
@aminvakil It looks like there is no
--no-ttyoption in Docker Compose 1, only in 2. That could explain why merging #1251 caused CI to start failing.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.
Bah ... but in that case why was CI green on #1251? 🤔