Update azure network watcher packages docker scenario #9940
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
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
cc @mrodm |
mrodm
changed the title
jsoriano
approved these changes
May 22, 2024
efd6
approved these changes
Jun 3, 2024
andrewkroh
added
Integration:azure_network_watcher_nsg
rcesar99999
pushed a commit
to rcesar99999/new_integrations
that referenced
this pull request
Feb 10, 2025
Update docker scenario for these packages to not use the full service name. Those containers can access the required service just with the service name defined in the same compose file.
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.
Proposed commit message
Update docker scenario for these packages to not use the full service name. Those containers can access the required service just with the service name in the same compose.
This will also help us to update how elastic-package manages these compose scenarios in the context of elastic/elastic-package#787
How to test this PR locally
Run system tests in both packages:
Related issues