If apply generates a cycle, plan should generate the same cycle, and graph should display the cycle #1651
Comments
phinze
added a commit
that referenced
this issue
Apr 23, 2015
Most CBD-related cycles include destroy nodes, and destroy nodes were all being pruned from the graph before staring the Validate walk. In practice this meant that we had scenarios that would error out with graph cycles on Apply that _seemed_ fine during Plan. This introduces a Verbose option to the GraphBuilder that tells it to generate a "worst-case" graph. Validate sets this to true so that cycle errors will always trigger at this step if they're going to happen. (This Verbose option will be exposed as a CLI flag to `terraform graph` in a second incoming PR.) refs #1651
|
With #1816 this is done. |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Because of the graph pruning that happens during
plan, there are many cycles that don't reveal themselves until the apply step. This breaks the plan/apply contract.I've been tracking this issue myself for a while now, and I've nearly completed a fix. But I wanted to file an issue to center the PR around.
The text was updated successfully, but these errors were encountered: