[WIP] Sync compose-schemas with upstream (docker/cli)#6642
Closed
thaJeztah wants to merge 1 commit intodocker:masterfrom
Closed
[WIP] Sync compose-schemas with upstream (docker/cli)#6642thaJeztah wants to merge 1 commit intodocker:masterfrom
thaJeztah wants to merge 1 commit intodocker:masterfrom
Conversation
Member
Author
|
This is obviously not finished (as the modified schema's (and the new |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
33a6749 to
752b63f
Compare
Contributor
|
Thanks for taking the time to create this issue/pull request! Unfortunately, Docker Compose V1 has reached end-of-life and we are not accepting any more changes (except for security issues). Please try and reproduce your issue with Compose V2 or rewrite your pull request to be based on the v2 branch and create a new issue or PR with the relevant Compose V2 information. |
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
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.
I wanted to update the compose-schemas to make sure they're in sync with upstream, but noticed there's changes in the schema in this repository that are not upstream.
Also; some of these patches were applied to older version, but are not in the latest (3.7) and upcoming (3.8) version.
We should make sure that both
docker stack deployanddocker-compose upvalidation is equal, otherwise files may work for one, but won't work for the other.If there's differences because of the implementation (Python vs Go), we should look if we can still use the same schema (if needed, upstream changes to docker/cli).
I was looking at reproducing the original issue () earlier this week (but not sure where I ended up, as I had to finish some other things 😂); I see I have these files still on my machine, which was what I was testing with;
I think I was testing if the problem presented itself on compose-file schema
3.6and3.7as it doesn't appear to have the fix from #4904, thus "should be failing"; here's the diff between 3.6 and 3.7 (before this patch);output:
Posting my test files here in case someone has time to verify.
docker-compose.yml:docker-compose.json:{ "version": "3.7", "services": { "web": { "image": "nginx:alpine", "labels": { "com.duo.access-gateway.builder.version": 89526235, "com.duo.access-gateway.code.version": "v1.4.4-beta0", "com.duo.access-gateway.built": "Fri, 02 Jun 2017 14:38:41 -0000", "com.duo.access-gateway.nil": null } } } }