-
Notifications
You must be signed in to change notification settings - Fork 16
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
Update use of schema API for the pull command #499
Conversation
src/commands/schema/pull.mjs
Outdated
|
||
logger.debug( | ||
`Pulling remote ${source} schema, version '${version}'.`, | ||
"schema pull", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@echo-bravo-yahoo do we have a preference of these being one word to simplify passing them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah i don't think it would work as expected unless it was a single or hyphenated word
Ticket(s): FE-6228
Problem
We do not pass in the
version
orstaged
params to calls to get schema files.Pulling active schema while a staged schema exists is possible, but we block it.
Solution
Pass in the version and staged parameters to
/schema/1/files/{filename}
endpoint calls.Update the confirmation message to indicate whether you are going to pull from active or staged schema.
Result
We can pull schema, whether it's staged or not. We utilize OCC with schema versions correctly.
Testing
Added tests that cover usage with the new behavior, including the --staged option.