Check service secrets existence #316
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
nicksieger
reviewed
Nov 1, 2022
Signed-off-by: Guillaume Lours <[email protected]>
…tUnnecessaryResources function Signed-off-by: Guillaume Lours <[email protected]>
glours
force-pushed
the
check-service-secrets
branch
from
48e4ed6 to
a9ba921
Compare
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.
Regarding the Compose Specification, a secret used at the service level should exist on the platform or be defined in the secrets section
Also fix bugs in
WithoutUnnecessaryResourcesthat created empty resources when a resource declared in service section weren’t existing in the top level declaration (secrets. volumes, networks, configs...)reference: docker/compose#9963