Add method to retrieve stack template, Avoid redirects #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 6 commits
November 9, 2015 12:10
Gets the template that was used to create the stack.
If you go to the path ../stacks/<stack_id>, you are (supposed to be) redirected to the proper path, ../stacks/<stack_name>/<stack_id>. Whether it's a bug with our deployment or OpenStack in general, the redirect for stack updates is broken. This allows the user to go directly to the correct path.
No need to join a single piece.
I forgot to add it.
params.error gets deleted, but the error callback needs to get passed through. Addresses issue: gabrielhurley#34
Adds the four actions supported by the orchestration API: suspend, resume, cancel_update, and check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows the user to retrieve the heat template that a stack was created with. The path was ending with a /, which breaks the API call, so I set the URL in templates.js.
If you go to the path ../stacks/<stack_id>, you are (supposed to be) redirected to the proper path, ../stacks/<stack_name>/<stack_id>. Whether it's a bug with our deployment or OpenStack in general, the redirect for stack updates doesn't work. This change allows the user to go directly to the correct path by specifying the stack name.