test: also allow mock_data and mock_resource blocks to generate data during planning #36317
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
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.
This is a quick follow up to #36227. We're extending the same functionality to the
mock_resourceandmock_datablocks that wasn't included in the last PR.There's a small refactor to compute the
override_duringvalue at the provider level instead of at the mock_data level. This means we can also use the value defined on the provider if we're loading mock data from external sources. In addition, the refactor lets us get rid of the boolean pointer fields that I found confusing. Now, the functions all require a default value that can be provided by the source value at the provider level.