justtrackio / terraform-aws-ecs-gosoline-monitoring

Terraform module which implements ECS gosoline app monitoring.
https://registry.terraform.io/modules/justtrackio/ecs-gosoline-monitoring/aws
Apache License 2.0
0 stars 0 forks source link

chore(deps): update terraform elasticstack to v0.6.2 - autoclosed #22

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
elasticstack (source) required_provider minor 0.5.0 -> 0.6.2

Release Notes

elastic/terraform-provider-elasticstack (elasticstack) ### [`v0.6.2`](https://togithub.com/elastic/terraform-provider-elasticstack/blob/HEAD/CHANGELOG.md#062---2023-06-19) [Compare Source](https://togithub.com/elastic/terraform-provider-elasticstack/compare/v0.6.1...v0.6.2) ##### Added - Logging of Kibana action connectors HTTP requests and responses when [Terraform logs are enabled](https://developer.hashicorp.com/terraform/internals/debugging). - Add `skip_destroy` flag to `elasticstack_fleet_agent_policy` resource ([#​357](https://togithub.com/elastic/terraform-provider-elasticstack/pull/357)) ### [`v0.6.1`](https://togithub.com/elastic/terraform-provider-elasticstack/blob/HEAD/CHANGELOG.md#061---2023-05-30) [Compare Source](https://togithub.com/elastic/terraform-provider-elasticstack/compare/v0.6.0...v0.6.1) ##### Added - Add `path_style_access` setting to `elasticstack_elasticsearch_snapshot_repository` on s3 repositories to enable path style access pattern ([#​331](https://togithub.com/elastic/terraform-provider-elasticstack/pull/331)) - Add `transform` field to `elasticstack_elasticsearch_watch` to allow for payload transforms to be defined ([#​340](https://togithub.com/elastic/terraform-provider-elasticstack/pull/340)) ##### Fixed - Fix error presented by incorrect handling of `disabled_features` field in `elasticstack_kibana_space` resource ([#​340](https://togithub.com/elastic/terraform-provider-elasticstack/pull/340)) ### [`v0.6.0`](https://togithub.com/elastic/terraform-provider-elasticstack/blob/HEAD/CHANGELOG.md#060---2023-05-24) [Compare Source](https://togithub.com/elastic/terraform-provider-elasticstack/compare/v0.5.0...v0.6.0) ##### Added - New resource `elasticstack_elasticsearch_enrich_policy` to manage enrich policies ([#​286](https://togithub.com/elastic/terraform-provider-elasticstack/pull/286)) ([Enrich API](https://www.elastic.co/guide/en/elasticsearch/reference/current/enrich-apis.html)) - New data source `elasticstack_elasticsearch_enrich_policy` to read enrich policies ([#​293](https://togithub.com/elastic/terraform-provider-elasticstack/pull/293)) ([Enrich API](https://www.elastic.co/guide/en/elasticsearch/reference/current/enrich-apis.html)) - Add 'mapping_coerce' field to index resource ([#​229](https://togithub.com/elastic/terraform-provider-elasticstack/pull/229)) - Add 'min_\*' conditions to ILM rollover ([#​250](https://togithub.com/elastic/terraform-provider-elasticstack/pull/250)) - Add support for Kibana connections ([#​226](https://togithub.com/elastic/terraform-provider-elasticstack/pull/226)) - **\[Breaking Change] Add 'deletion_protection' field to index resource** to avoid unintentional deletion. ([#​167](https://togithub.com/elastic/terraform-provider-elasticstack/pull/167)) - To delete index resource, you'll need to explicitly set `deletion_protection = false` as follows. ```terraform resource "elasticstack_elasticsearch_index" "example" { name = "example" mappings = jsonencode({ properties = { field1 = { type = "text" } } }) deletion_protection = false } ``` - Add `elasticstack_kibana_space` for managing Kibana spaces ([#​272](https://togithub.com/elastic/terraform-provider-elasticstack/pull/272)) - Add `elasticstack_elasticsearch_transform` for managing Elasticsearch transforms ([#​284](https://togithub.com/elastic/terraform-provider-elasticstack/pull/284)) - Add `elasticstack_elasticsearch_watch` for managing Elasticsearch Watches ([#​155](https://togithub.com/elastic/terraform-provider-elasticstack/pull/155)) - Add `elasticstack_kibana_alerting_rule` for managing Kibana alerting rules ([#​292](https://togithub.com/elastic/terraform-provider-elasticstack/pull/292)) - Add client for communicating with the Fleet APIs ([#​311](https://togithub.com/elastic/terraform-provider-elasticstack/pull/311)]) - Add `elasticstack_fleet_enrollment_tokens` and `elasticstack_fleet_agent_policy` for managing Fleet enrollment tokens and agent policies ([#​322](https://togithub.com/elastic/terraform-provider-elasticstack/pull/322)]) - Add `elasticstack_fleet_output` and `elasticstack_fleet_server_host` for managing Fleet outputs and server hosts ([#​327](https://togithub.com/elastic/terraform-provider-elasticstack/pull/327)]) - Add `elasticstack_kibana_action_connector` for managing Kibana action connectors ([#​306](https://togithub.com/elastic/terraform-provider-elasticstack/pull/306)) ##### Fixed - Updated unsupported queue_max_bytes_number and queue_max_bytes_units with queue.max_bytes ([#​266](https://togithub.com/elastic/terraform-provider-elasticstack/issues/266)) - Respect `ignore_unavailable` and `include_global_state` values when configuring SLM policies ([#​224](https://togithub.com/elastic/terraform-provider-elasticstack/pull/224)) - Refactor API client functions and return diagnostics ([#​220](https://togithub.com/elastic/terraform-provider-elasticstack/pull/220)) - Fix not to recreate index when field is removed from mapping ([#​232](https://togithub.com/elastic/terraform-provider-elasticstack/pull/232)) - Add query params fields to index resource ([#​244](https://togithub.com/elastic/terraform-provider-elasticstack/pull/244)) - Properly handle errors which occur during provider execution ([#​262](https://togithub.com/elastic/terraform-provider-elasticstack/pull/262)) - Correctly handle empty logstash pipeline metadata in plan diffs ([#​256](https://togithub.com/elastic/terraform-provider-elasticstack/pull/256)) - Fix error when logging API requests in debug mode ([#​259](https://togithub.com/elastic/terraform-provider-elasticstack/pull/259)) - **\[Breaking Change] Change `pipeline_metadata` type from schema.TypeMap to schema.TypeString**. This is to fix an error caused by updates to Logstash Pipelines outside of TF ([#​278](https://togithub.com/elastic/terraform-provider-elasticstack/issues/278)) - To use the updated `pipeline_metadata` field, you'll need to encapsulate any Terraform configuration with **jsonencode{}** as follows: ```terraform resource "elasticstack_elasticsearch_logstash_pipeline" "example" { name = "example" pipeline = <<-EOF input{} filter{} output{} EOF pipeline_metadata = jsonencode({ type = "logstash_pipeline" version = 1 }) } ``` - If migrating existing resources in state from a previous version of the provider, then you will need to remove the reference to the resources in state before reapplying / reimporting: - Run `terraform state rm` against your logstash pipelines (https://developer.hashicorp.com/terraform/cli/commands/state/rm) - Ensure any definitions of the `pipeline_metadata` field in your resource definitions have been encapsulated with `jsonencode()` as mentioned above. - EITHER - run `terraform plan` - run `terraform apply` - OR - reimport the resources into state using `terraform import` (https://developer.hashicorp.com/terraform/cli/import) - Fix order of `indices` field in SLM ([#​326](https://togithub.com/elastic/terraform-provider-elasticstack/pull/326))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

github-actions[bot] commented 1 year ago

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.