8000 Reconcile docker-compose shcema on docker/cli vs docker/compose · Issue #7047 · docker/compose · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Reconcile docker-compose shcema on docker/cli vs docker/compose #7047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ndeloof opened this issue Nov 22, 2019 · 2 comments
Closed

Reconcile docker-compose shcema on docker/cli vs docker/compose #7047

ndeloof opened this issue Nov 22, 2019 · 2 comments
Labels

Comments

@ndeloof
Copy link
Contributor
ndeloof commented Nov 22, 2019

Docker Compose schema on https://github.com/docker/cli/tree/master/cli/compose/schema/data is considered by maintainers as the leading one, and should be the place we use to any proposal for schame enhancements.

We need to double check https://github.com/docker/compose/tree/master/compose/config didn't diverge, and enforce we don't make changes here that have not been already applied to the leading schema.

Idealy we should find a mechanism to avoid duplication, and define a canonical location for compose schemas.

@stale
Copy link
stale bot commented May 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 20, 2020
@stale
Copy link
stale bot commented May 27, 2020

This issue has been automatically closed because it had not recent activity during the stale period.

@stale stale bot closed this as completed May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant
0