Skip to content
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

Schema management improvement #35

Open
damianoneill opened this issue Jan 2, 2018 · 3 comments
Open

Schema management improvement #35

damianoneill opened this issue Jan 2, 2018 · 3 comments

Comments

@damianoneill
Copy link
Contributor

This section on the README.md –

_

Schema Files

Note that schema stored here is just a cache for helping development. Developers should make sure download latest schema from http://github.com/Juniper/contrail-api-client

JSON version stored in public/schema.json

_

If the intent is that the user always uses the latest schema managed under a different repository, why don’t you just use a git submodule for this?

@nati
Copy link
Contributor

nati commented Jan 2, 2018

Contrail repos are under migration now. so I would like to use git subtree once main repo get ready

git sub tree: https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree

@damianoneill
Copy link
Contributor Author

I'm not opinionated on either option, other than it should be done rather than asking users to copy from a different repo.

@nati
Copy link
Contributor

nati commented Jan 2, 2018

kk let's keep open this issue until this issue get fixed.

@nati nati changed the title Git Submodule Git SubTree support Jan 2, 2018
@nati nati changed the title Git SubTree support Schema management improvement Jan 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants