Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update semantics - is there a way to to replay replacement details? #125

Open
cveld opened this issue May 8, 2023 · 0 comments
Open

Update semantics - is there a way to to replay replacement details? #125

cveld opened this issue May 8, 2023 · 0 comments

Comments

@cveld
Copy link

cveld commented May 8, 2023

Is there a way to relay to the terraform cli that a particular change on an input is triggering a replacement?

E.g. current state:

{
   "id": 3,
   "somereference": 4
}

The user changes somereference from 4 to 5 and runs a plan:

Message:

{
   "id": 3,
   "somereference": 4 -> 5 # causes replacement
}

In the current version I am using, I only see two ways:

  1. the read operation could return an error, faking that the resource does not exist and must be created freshly. Downside is that the original resource is not removed
  2. the update operation could replace the resource transparently. downside would be that the user is not expecting this based on the generated plan

Provider version: 1.7.10
terraform cli version: 1.4.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant