Eval operations at execution where state unknown #995
Closed
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
…cution This is specifically to catch cases where there is no current remote state but it is likely that this may change due to hidden side effects from other operations. See: #805 for more context.
This means that other preceding operations, ie package installs, will not be incorrectly handled by `files` operation calls. Specifically this makes the various `assume_present` workaround arguments redundant.
This means nested operation calls may yield the flag to be re-evaluated at execution.
|
Cancelling this in favour of #996, there’s just too much magic already and this change adds yet more. V3 will radically simplify and address these issues properly. |
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.
Closes: #805