-
Notifications
You must be signed in to change notification settings - Fork 127
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
feat(service_version): Add support for environments. #542
Conversation
👋🏻 I don't see this API behaviour documented: What does the additional path segment do with regards to service activation? |
The API docs are still in progress. |
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.
This looks fine to me other than properly capitalizing Fastly :-)
We'll wait to merge this until the API documentation has been merged, partially to ensure that the terminology ("Environment") matches up.
I believe this is ready but asked for a second opinion :-) |
…ice-versions. Add 'environments' details to service and service-version API responses.
cd46f20
to
20d8b59
Compare
This has been simplified to remove the 'stage' and 'unstage' wrappers. It now only adds the optional 'Environment' parameter to 'Activate'/'Deactivate', and exposes the 'Environments' details included in API responses when service/version details are obtained. |
Also Activating and Deactivating an Service Version to and from a particular Environment.
It's possible that we don't want the StageVerson and UnstageVersion shortcuts.