Bug: launch single stack with !stack_output and --ignore-dependencies
#778
Comments
ngfgrant
added a commit
that referenced
this issue
Jul 4, 2019
This commit fixes an issue where a users attempts to launch a single stack that utilises the `stack_output_resolver` with the `--ignore-dependencies`. Previously, with `--ignore-dependencies` set, any dependencies that arose through `!stack_output_resolver` would not be added to `stack.dependencies` and the `next()` function in `StackOutput.resolve()` would raise a `StopIteration` as the stack.dependencies list would be empty. This commit handles the stack_output by utilising the argument passed into `stack_output`. [Resolves #778]
9 tasks
ngfgrant
added a commit
that referenced
this issue
Jul 4, 2019
This commit fixes an issue where a users attempts to launch a single stack that utilises the `stack_output_resolver` with the `--ignore-dependencies`. Previously, with `--ignore-dependencies` set, any dependencies that arose through `!stack_output_resolver` would not be added to `stack.dependencies` and the `next()` function in `StackOutput.resolve()` would raise a `StopIteration` as the stack.dependencies list would be empty. This commit handles the stack_output by utilising the argument passed into `stack_output`. [Resolves #778]
chhibber
pushed a commit
to chhibber/sceptre
that referenced
this issue
Aug 20, 2019
This commit fixes an issue where a users attempts to launch a single stack that utilises the `stack_output_resolver` with the `--ignore-dependencies`. Previously, with `--ignore-dependencies` set, any dependencies that arose through `!stack_output_resolver` would not be added to `stack.dependencies` and the `next()` function in `StackOutput.resolve()` would raise a `StopIteration` as the stack.dependencies list would be empty. This commit handles the stack_output by utilising the argument passed into `stack_output`. [Resolves Sceptre#778]
chhibber
pushed a commit
to chhibber/sceptre
that referenced
this issue
Aug 20, 2019
This commit fixes an issue where a users attempts to launch a single stack that utilises the `stack_output_resolver` with the `--ignore-dependencies`. Previously, with `--ignore-dependencies` set, any dependencies that arose through `!stack_output_resolver` would not be added to `stack.dependencies` and the `next()` function in `StackOutput.resolve()` would raise a `StopIteration` as the stack.dependencies list would be empty. This commit handles the stack_output by utilising the argument passed into `stack_output`. [Resolves Sceptre#778]
|
any progress on this? would say that is better to have the constrain of the region that it break? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an issue where a users attempts to launch a single stack that utilises the
stack_output_resolverwith the--ignore-dependencies.With
--ignore-dependenciesset, any dependencies that arise through!stack_output_resolverwould not be added tostack.dependenciesand thenext()function inStackOutput.resolve()would raise aStopIterationas the stack.dependencies list would be empty.The text was updated successfully, but these errors were encountered: