Bot releases are hidden (Show)
FEATURES:
name
to allow searching by exact deployment name. (#797)ENHANCEMENTS:
BUG FIXES:
self
when it's been explicitly configured. (#789)elasticsearch
attribute contains both strategy
and snapshot_source
.elasticsearch
defines snapshot
with repository
that doesn't contain reference
. (#719)Published by dimuon about 1 year ago
FEATURES:
ENHANCEMENTS:
BUG FIXES:
Published by tobio about 1 year ago
FEATURES:
BUG FIXES:
Published by tobio over 1 year ago
ENHANCEMENTS:
Published by tobio over 1 year ago
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:
Existing resources should be imported. Please see NOTES below and README for more details.
NOTES
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.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.Published by tobio over 1 year ago
Published by elasticcloudclients about 2 years ago
Published by elasticcloudclients over 2 years ago
Published by elasticcloudclients over 2 years ago
Published by elasticcloudclients about 3 years ago
FEATURES:
ec_deployment_elasticsearch_keystore
resource which allows creating and updating Elasticsearch keystore settings. (#364)ENHANCEMENTS:
deployments.#.elasticsearch_ref_id
, deployments.#.kibana_ref_id
, deployments.#.apm_ref_id
, deployments.#.enterprise_search_ref_id
to the data source. (#380)deployments.#.name
and deployments.#.alias
to the data source. (#362)BUG FIXES:
ec_deployment.elasticsearch.remote_cluster
block to schema.TypeSet
to allow specifying the blocks in any order. (#368)elasticsearch.config.user_settings_* = null
would result in a provider panic. (#355)version
argument value updated as if all resources were upgraded. Attempts to retry the upgrade would fail since the version difference was not detected. (#371)Published by elasticcloudclients over 3 years ago
BUG FIXES:
resource/ec_deployment: Fixes a bug which made ec_deployment version upgrades return an API error stating: node_roles must be provided for all elasticsearch topology elements or for none of them. (#329)
Published by elasticcloudclients over 3 years ago
FEATURES:
10
in the number of deployments returned by the search request. (#300)elasticsearch.autoscale
("true"
or "false"
) and an elasticsearch.topology.autoscaling
block to modify the default autoscaling policies. For more information, refer to the documentation examples. (#296)alias
. (#298)ENHANCEMENTS:
BUG FIXES:
Published by elasticcloudclients over 3 years ago
BREAKING CHANGES:
apm.version
, enterprise_search.version
and kibana.version
computed fields. (#266)elasticsearch.toplogy.id
has been added, it needs to be set to all explicit Elasticsearch topology declarations. A node_roles
computed field has been added to the schema and cannot be overridden by the user, versions >=7.10.0
will be automatically migrated by the provider to use node_roles
from the node_type_*
settings, these will be removed from the state. When node_type_*
fields are explicitly set in the terraform configuration they need to be unset manually by the user. Additionally, it removes the elasticsearch.version
computed field. (#253)FEATURES:
ec_extension
which allows users to mange custom Elasticsearch bundles and plugins (#216)ENHANCEMENTS:
ec_deployment
datasource (#244)elasticsearch.extension
block which can be used to enable custom Elasticsearch bundles or plugins that have previously been uploaded. (#264)BUG FIXES:
-dev
tag prior to releasing (#235)Published by elasticcloudclients almost 4 years ago
NOTES
The Elastic Cloud Terraform provider allows you to provision Elastic Cloud deployments on any Elastic Cloud platform, whether it’s Elasticsearch Service or Elastic Cloud Enterprise.
This functionality is in beta and is subject to change. The design and code are less mature than official GA features and are being provided as-is with no warranties.
FEATURES