record: Move validation by type out of CustomizeDiff. #671
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.
Fixes: #670
We're doing validation inside of a
CustomizeDiff
function. The interpolated values are not available there on plan. This prevents user from doing things like referencing a database cluster's port in a SRV record. This is similar to hashicorp/terraform-provider-consul#260 This PR moves that validation to later in the process.This has one side effect. The reason for using a
CustomizeDiff
for something like this is that it allows you to error out early before any of the plan runs. Now the error will not happen until the record is being created. I don't love that, but not sure I see a better way to do it.