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

fix: lifecycle changes for bug 164 #166

Conversation

krystan
Copy link

@krystan krystan commented Apr 9, 2020

Description

Stops the clobbering of volume tags if you have EBS volumes attached with their own tags

Motivation and Context

Fixes a bug triggered by an outstanding terraform issue:
hashicorp/terraform-provider-aws#770

closes #164

Breaking Changes

None

How Has This Been Tested?

Ran in live code from my repository, tags no longer flip-flopped between instance tags and EBS volume tags, resources kept their own tags.

@gillg
Copy link

gillg commented Apr 19, 2020

I was gone to propose the same MR ! Thanks !

Just, I think it will be better for retrocompatibility to add a dynamic "lifecycle" but it's not supported by terraform for now...
So for me it's better than nothing and cause less bugs.

Actually my tags are switching at evry runs... And they are important for automation tasks.

@krystan
Copy link
Author

krystan commented Apr 19, 2020

I was gone to propose the same MR ! Thanks !

Just, I think it will be better for retrocompatibility to add a dynamic "lifecycle" but it's not supported by terraform for now...
So for me it's better than nothing and cause less bugs.

Actually my tags are switching at evry runs... And they are important for automation tasks.

The reason I put this in was the same my tags changed every run and automation tasks used them, this fixes that.

@krystan krystan closed this Apr 19, 2020
@krystan krystan reopened this Apr 19, 2020
@krystan
Copy link
Author

krystan commented Apr 19, 2020

accidently closed request (sorry) reopening

@tbugfinder
Copy link

tbugfinder commented May 7, 2020

Couldn't lifecycle be exposed as an optional variable so that everybody could provide input needed?

@antonbabenko
Copy link
Member

@tbugfinder This is not possible in Terraform. lifecycle is a meta-argument in Terraform and has a special purpose.

@krystan
Copy link
Author

krystan commented May 13, 2020

So I do appreciate this is a sponsored project but what is the verdict on this?

@antonbabenko
Copy link
Member

Is this a sponsored project? :) I didn't know that, but everyone is more than welcome - https://github.com/sponsors/antonbabenko

Regarding the verdict on this, the proposed PR is going to break functionality many users rely on so we can't merge it as is.

We need to wait for the time when Terraform allows us to use variables in lifecycle.

Meanwhile, please use your own fork.

@krystan
Copy link
Author

krystan commented May 14, 2020

Closing pull request as per maintainer feedback.

@krystan krystan closed this May 14, 2020
@github-actions
Copy link

github-actions bot commented Nov 9, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Attached EBS Volume tags flip flop between volume_tags for instance on each apply
4 participants