Removes operations, resources_created, user_output fields from the Global Context and Template class #114
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.
Description
Based on offline discussion, the
State
Index (issue #74 ) will be responsible for storing theresources_created
anduser_outputs
field instead of theGlobal Context Index
, and will be returned by theStatus
API upon the completion of a provision workflow. This PR modifies theTemplate
class andGlobal Context Index
mapping to reflect this.Additionally, the
operations
field has been removed from the template/Global Context, as it is currently not used. (May add it back in once theOrchestrate
API is exposed)The following use case template is an example following the new format :
Issues Resolved
A continuation of issue #105
Part of #88
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.