Bump elastic/ec from 0.1.1 to 0.6.0 in /modules/elastic/cluster

[dependabot]

Bumps elastic/ec from 0.1.1 to 0.6.0.

Release notes

Sourced from elastic/ec's releases.

v0.6.0

FEATURES:

Migration to TF Plugin Framework

BREAKING CHANGE:

ec_deployment uses a new schema now in order to fix the crucial defects around autoscaling/topologies:

• elastic/terraform-provider-ec#336
• elastic/terraform-provider-ec#445
• elastic/terraform-provider-ec#466
• elastic/terraform-provider-ec#467

Existing resources should be imported. Please see NOTES below and README for more details.

NOTES

• Older versions of terraform CLI can report errors with the provider 0.6.0. Please make sure to update Terraform CLI to the latest version.
• ec_deployment has a new schema now but state upgrade is not implemented. The recommended way to proceed with existing TF resources is state import. However, this doesn't import user passwords and secret tokens.
• After import, the next plan command may try to delete some empty or zero size attributes, e.g. it can try to delete empty elasticsearch config or cold tier attributes if configuration doesn't define them and cold tier size is zero. It should not be a problem. You can either execute the plan (the only result should be an updated Terraform state while the deployment should remain the same) or add empty cold tier and config elasticsearch attributes to the configuration.
• The migration is based on 0.4.1, so all changes from 0.5.0 and 0.5.1 are omitted.

v0.5.1

No release notes provided.

v0.5.0

No release notes provided.

v0.4.1

No release notes provided.

v0.4.0

No release notes provided.

v0.3.0

FEATURES:

• New Resource: resource/ec_deployment_elasticsearch_keystore: Adds a new ec_deployment_elasticsearch_keystore resource which allows creating and updating Elasticsearch keystore settings. (#364)

ENHANCEMENTS:

• datasource/ec_deployments: Adds four new fields, deployments.#.elasticsearch_ref_id, deployments.#.kibana_ref_id, deployments.#.apm_ref_id, deployments.#.enterprise_search_ref_id to the data source. (#380)
• datasource/ec_deployments: Adds two new fields, deployments.#.name and deployments.#.alias to the data source. (#362)
• resource/ec_deployment_traffic_filter: Add support for Azure Private Link traffic rules. (#340)

BUG FIXES:

• resource/ec_deployment: Changes the ec_deployment.elasticsearch.remote_cluster block to schema.TypeSet to allow specifying the blocks in any order. (#368)
• resource/ec_deployment: Fix bug where setting any of the elasticsearch.config.user_settings_* = null would result in a provider panic. (#355)

... (truncated)

Changelog

Sourced from elastic/ec's changelog.

0.6.0 (Feb 28, 2023)

FEATURES:

Migration to TF Plugin Framework

BREAKING CHANGES:

New schema for ec_deployment. Existing resources should be imported. Please see NOTES below and README for more details.

BUG FIXES:

#336 #445 #466 #467

NOTES

• Older versions of terraform CLI can report errors with the provider 0.6.0. Please make sure to update Terraform CLI to the latest version.
• ec_deployment has a new schema now but state upgrade is not implemented. The recommended way to proceed with existing TF resources is state import. However, this doesn't import user passwords and secret tokens.
• After import, the next plan command may try to delete some empty or zero size attributes, e.g. it can try to delete empty elasticsearch config or cold tier if configuration doesn't define them and cold tier size is zero. It should not be a problem. You can eigher execute the plan (the only result should be updated Terraform state while the deployment should stay the same) or add empty cold tier and config attributes to the configuration.
• The migration is based on 0.4.1, so all changes from 0.5.0 and 0.5.1 are omitted.

0.5.1 (Feb 15, 2023)

FEATURES:

• resource/deployment: Utilise the template migration API to build the base update request when changing deployment_template_id. This results in more reliable changes between deployment templates. (#547)

0.5.0 (Oct 12, 2022)

FEATURES:

• datasource/privatelink: Adds data sources to obtain AWS/Azure Private Link, and GCP Private Service Connect configuration data. (#533)
• resource/deployment: Adds fleet_https_endpoint and apm_https_endpoint to integrations server resources. This allows consumers to explicitly capture service urls for dependent modules. (#548)
• resource/elasticsearch: Adds support for the strategy property to the elasticsearch resource. This allows users to define how different plan changes are coordinated. (#507)

BUG FIXES:

• resource/deployment: Correctly restrict stateless (Kibana/Enterprise Search/Integrations Server) resources to a single topology element. Fixes a provider crash when multiple elements without an instance_configuration_id were specified. (#536)
• resource/elasticsearchkeystore: Correctly delete keystore items when removed from the module definition. (#546)
• resource: Updates all nested field accesses to validate type casts. This prevents a provider crash when a field is explicitly set to null. (#534)

0.4.1 (May 11, 2022)

BREAKING CHANGES:

... (truncated)

Commits

• af221f7 Update CHANGELOG.md and NOTICE
• 56f18cf fix(deps): update module github.com/hashicorp/terraform-plugin-log to v0.8.0 ...
• 9574ed6 Update CHANGELOG.md and NOTICE
• 249f582 chore(deps): update peterjgrainger/action-create-branch action to v2.4.0 (#566)
• 89f824d Update CHANGELOG.md and NOTICE
• 269648d Feature/530/migrate to plugin framework (#567)
• b9c45c5 Update CHANGELOG.md and NOTICE
• 1b98801 Bump goreleaser
• 3c99d6c Update CHANGELOG.md and NOTICE
• 7f8303e Post 0.5.1 version bump
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[tom-reinders]

@dependabot rebase

[dependabot]

Superseded by #319.