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

Allow triggers for all resource types to enable rebuilding resources on trigger changes #10586

Closed
bbakersmith opened this issue Dec 7, 2016 · 4 comments
Labels

Comments

@bbakersmith
Copy link

Feature request.

Would love to see the null_resource "triggers" be made available to other resource types, so you could specify that if ${var.foobar} changes, the resource should be rebuilt.

This would work something like...

resource "aws_s3_bucket_object" "foo" {
    ...
}

resource "aws_instance" "bar" {
    triggers {
        new_application_version = "${aws_s3_bucket_object.foo.etag}"
    }
    ...
}

...and should take the place of hacky workarounds like injecting the etag of the above s3 object into some rebuild-requiring field of the aws_instance. Alternately, being able to specify that any and all changes to a given resource should trigger a full rebuild would make such hacky workarounds easier because then any changed field could be used to trigger a rebuild.

@mitchellh mitchellh added the bug label Dec 8, 2016
@mitchellh
Copy link
Contributor

A feature request for this already exists, I believe the proposal was to make depends_on do this but I think the plan is to make a new metaparameter that is just like depends_on but this behavior... at any rate if you search core+enhancement it should pop up.

@bbakersmith
Copy link
Author

Thanks @mitchellh - I searched for such an issue before, and again now, but this is the closest I've found, is this the one you mean?

#113

@mitchellh
Copy link
Contributor

Thats it! :)

@ghost
Copy link

ghost commented Apr 19, 2020

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants