Fix: rule_id
attribute ignored for elasticstack_kibana_alerting_rule
resource
#626
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.
Similar to #622, currently the
rule_id
attribute of aelasticstack_kibana_alerting_rule
is ignored; we just pass in an empty string:terraform-provider-elasticstack/internal/clients/kibana/alerting.go
Line 87 in 85accb6
This commit fixes this by passing the
rule_id
attribute's value to the client's API call, if unset, we pass an empty string - the same as existing behaviour.Note that there's a bug in the Alerting OpenAPI spec that means it's missing the 409 response, so I had to add a manual conflict check upon creation.
We can remove this check when elastic/kibana#183223 is closed, and the swagger version is bumped:
terraform-provider-elasticstack/Makefile
Line 14 in 85accb6
Tested manually with this TF file: