Playground needs optionally external network #2564
Merged
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
Signed-off-by: Jason Sherman <tools@usingtechnolo.gy>
|
Kudos, SonarCloud Quality Gate passed!
|
dbluhm
approved these changes
Oct 25, 2023
|
@dbluhm - Sorry about all these small fixes. Thanks for reviewing and merging them! |
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.
Sigh... when documenting aries-mediator-service / redid-pq-demo and running through the instructions, I needed to make the playground network external.
Unclear why it worked fine with the base mediator service and it's network but regardless, this is needed to allow the mediator service with redis demo to work.
Note that the
ELK_NETWORK_NAMEwill always be an external network so adding that notation to always betrue.