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

template_file not compatible with fields with a StateFunc #3864

Closed
ColinHebert opened this issue Nov 11, 2015 · 7 comments
Closed

template_file not compatible with fields with a StateFunc #3864

ColinHebert opened this issue Nov 11, 2015 · 7 comments

Comments

@ColinHebert
Copy link
Contributor

It seems currently (terraform 6.6) not possible to use the content of a template_file (or any terraform reference for that matter) in a field with a StateFunc.

This causes #3076 has attempted to be fixed in #3331

My gut feeling is that the StateFunc is applied too early and there is no type for the terraform reference to be processed:
https://github.com/hashicorp/terraform/blob/master/helper/schema/schema.go#L922

The issue mentioned above is with the policy of an S3 bucket, but it also applies to the user_data of a aws_launch_configuration (processed into a sha1 before the content of the file has been imported)

@Fodoj
Copy link

Fodoj commented Nov 16, 2015

@ColinHebert this PR introduced this bug #2788 If you roll it back and recompile terraform then everything should be fine

@ColinHebert
Copy link
Contributor Author

@mitchellh Can you check the PR @Fodoj mentioned above, is reverting it the way forward?

@ColinHebert
Copy link
Contributor Author

@jen20 @mitchellh any news regarding this?

@ColinHebert
Copy link
Contributor Author

@catsby @jen20 @radeksimko any update in this issue?

@dferramosi
Copy link

Any update at all? I am running into this as well, and am now getting serious pressure to fix it or stop using terraform as we need to increase instances and that changes user-data

@ColinHebert
Copy link
Contributor Author

I can't reproduce this problem anymore on my side.

@ghost
Copy link

ghost commented Apr 25, 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 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants