-
Notifications
You must be signed in to change notification settings - Fork 70
feat(service-version): Add JSON support to service-version clone command #1550
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
Conversation
As part of issue 1353, the service-version clone command is missing the option for JSON output and to use it in scripts the output need to be parsed. This commit adds functionality to accept the --json argument to the service-version clone command and outputs the appropriate format. Unit tests passing.
b5d87db to
16f3950
Compare
|
The test failure on Windows is not related to the contents of this PR - that sort of 'race condition' failure happens sometimes on Windows but it hasn't been a priority for us to fix it. Feel free to just re-run the failing job and it will almost certainly succeed. |
kpfleming
left a comment
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.
Some small changes needed, but overall this looks very good!
e367d5e to
d6b139c
Compare
|
Looks great, I'll merge it now! |
Change summary
Added JSON support to service-version clone command as reported in issue #1353.
NOTE: Unable to reproduce the ordering issue/race condition that the customer reported by running the list command immediately after the clone command. We ran this sequence multiple times, but each time the list was returned in the expected order, with the newly cloned service-version listed last.
All Submissions:
Changes to Core Features:
User Impact
Are there any considerations that need to be addressed for release?
No breaking changes.