providers/fastly Add request_condition to backend definition #11238
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.
Exposes request_condition option on the service's backend definition.
Fastly's doc for backend definition:
https://docs.fastly.com/api/config#backend
The option is already built into the go-fastly and just needed to be available in TF's syntax.
The one thing I'm not sure about in terms of terraform's responsibilities was, if terraform itself should be validating if the condition was already defined (required by Fastly's API) or should we let Fastly handle it and error out (which it should do). That would require us to carry a list of created condition's down to backends creation block for reference.