fix: allow generated logs to have unique hostnames #29
Conversation
This file contains 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
Red-GV
force-pushed
the
unique-log-names
branch
2 times, most recently
from
882cd1a
to
0c20a90
Compare
|
@Red-GV I think you found a bug in the docker workflow ... fixing ... edit: the issue is fixed in |
xperimental
reviewed
Aug 28, 2023
Red-GV
force-pushed
the
unique-log-names
branch
from
0c20a90
to
96d50ab
Compare
|
wfm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR changes the generator to append a random integer to the hostname value in the log message in order to ensure uniqueness of the field.
cc: @jcantrill