Merge compose extensions. #768
Merged
Conversation
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
ndeloof
approved these changes
Apr 9, 2025
|
for legal reasons, contributor's commit must be signed-off. Please amend and force-push your branch By the way, what are you using x- extension fields for? |
Fixes docker/compose#12724. Signed-off-by: Florian Apolloner <florian@apolloner.eu>
apollo13
force-pushed
the
fb-merge-compose-extensions
branch
from
5cbbed9 to
0d4b187
Compare
Done, sorry.
I am building my PaaS infrastructure for my homeservers & vms. Basically some ansible scripts that deploy compose units and I am using If this is something extensions are not supposed to be used for, please tell me and I will think of a different way. But currently this is shaping out really nicely. |
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.
Fixes docker/compose#12724.