Fix: rule_id attribute ignored for elasticstack_kibana_alerting_rule resource

CHANGELOG.md

@@ -6,6 +6,7 @@
 - Prevent `elasticstack_kibana_space` to attempt the space recreation if `initials` and `color` are not provided. ([#606](https://github.com/elastic/terraform-provider-elasticstack/pull/606))
 - Prevent a provider panic in `elasticstack_kibana_data_view` when a `field_format` does not include a `pattern`. ([#619](https://github.com/elastic/terraform-provider-elasticstack/pull/619/files))
 - Fixed a bug where the `id` attribute for `elasticstack_kibana_slo` resources was ignored by renaming the attribute to `slo_id`. ([#622](https://github.com/elastic/terraform-provider-elasticstack/pull/622))
+- Fixed a bug where the `rule_id` attribute for `elasticstack_kibana_alerting_rule` was ignored. ([#626](https://github.com/elastic/terraform-provider-elasticstack/pull/626))
 
 ### Added
 

generated/alerting/.openapi-generator/VERSION

@@ -1 +1 @@
-7.1.0-SNAPSHOT
+7.0.1

generated/alerting/README.md

@@ -36,15 +36,15 @@ Default configuration comes with `Servers` field that contains server objects as
 
 ### Select Server Configuration
 
-For using other server than the one defined on index 0 set context value `alerting.ContextServerIndex` of type `int`.
+For using other server than the one defined on index 0 set context value `sw.ContextServerIndex` of type `int`.
 
 ```golang
 ctx := context.WithValue(context.Background(), alerting.ContextServerIndex, 1)
 ```
 
 ### Templated Server URL
 
-Templated server URL is formatted using default variables from configuration or from context value `alerting.ContextServerVariables` of type `map[string]string`.
+Templated server URL is formatted using default variables from configuration or from context value `sw.ContextServerVariables` of type `map[string]string`.
 
 ```golang
 ctx := context.WithValue(context.Background(), alerting.ContextServerVariables, map[string]string{
@@ -58,7 +58,7 @@ Note, enum values are always validated and all unused variables are silently ign
 
 Each operation can use different server URL defined using `OperationServers` map in the `Configuration`.
 An operation is uniquely identified by `"{classname}Service.{nickname}"` string.
-Similar rules for overriding default operation server index and variables applies by using `alerting.ContextOperationServerIndices` and `alerting.ContextOperationServerVariables` context maps.
+Similar rules for overriding default operation server index and variables applies by using `sw.ContextOperationServerIndices` and `sw.ContextOperationServerVariables` context maps.
 
 ```golang
 ctx := context.WithValue(context.Background(), alerting.ContextOperationServerIndices, map[string]int{
@@ -168,7 +168,7 @@ Authentication schemes defined for the API:
 Example
 
 ```golang
-auth := context.WithValue(context.Background(), alerting.ContextBasicAuth, alerting.BasicAuth{
+auth := context.WithValue(context.Background(), sw.ContextBasicAuth, sw.BasicAuth{
     UserName: "username",
     Password: "password",
 })
@@ -188,8 +188,8 @@ Example
 ```golang
 auth := context.WithValue(
 		context.Background(),
-		alerting.ContextAPIKeys,
-		map[string]alerting.APIKey{
+		sw.ContextAPIKeys,
+		map[string]sw.APIKey{
 			"ApiKey": {Key: "API_KEY_STRING"},
 		},
 	)

generated/alerting/api/openapi.yaml

@@ -3619,5 +3619,5 @@ components:
       type: http
     apiKeyAuth:
       in: header
-      name: Authorization
+      name: ApiKey
       type: apiKey