Experiment/topologies set #573
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduce mux and port the provider to v6.
Migrate data sources to terraform-provider-framework
…m-provider-framework
Migrate resource ec_deployment_traffic_filter_association to terraform-provider-framework
…ork-0.12 Update to terraform-plugin-framework 0.12 and fix import order
…ramework The behavior of the default_value plan_modifier changes, so it also applies default values when the value has been explicitly specified before. Unit test timeout increased. Switch to v6 provider in tests.
Migrate resource ec_deployment_traffic_filter to terraform-provider-framework
* Use ListNestedAttributes for nested schemas in datasource ec_stack * Use ListNestedAttributes for nested schemas in datasource ec_deployment * Use blocks and ListNestedAttributes for nested schemas in datasource ec_deployments
…ugin-framework (#10) Co-authored-by: Pascal Hofmann <pascal.hofmann.ext@gec.io>
Update dependencies and remove external provider workaround from migration tests
#12) * Migrate resource ec_deployment_extension to terraform-plugin-framework * Remove useless use of ec.Bool() and ec.String() Co-authored-by: Pascal Hofmann <pascal.hofmann.ext@gec.io>
…te-to-plugin-framework
|
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
|
The current TF core logic (TF client 1.3.7) makes it impossible to use sets with more than one computed + optional underlying attributes that means, in particular, that Elasticsearch topology (where a tier object has more than one computed and optional attributes) cannot be represented by a set ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
An alternative to #567 approach to Elasticsearch topology. The PR represents it as a set.
The PR is still in the experimental stage!!!
Related Issues
Motivation and Context
How Has This Been Tested?
Types of Changes
Readiness Checklist