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

Upgrade to 0.12 syntax #90

Closed
wants to merge 3 commits into from
Closed

Upgrade to 0.12 syntax #90

wants to merge 3 commits into from

Conversation

fearoffish
Copy link

This upgrade handles the syntax change to terraform 0.12 syntax. I'm only using this to create single instance calls at the moment though, with no use of count.

@yasn77
Copy link

yasn77 commented May 29, 2019

@fearoffish Looks like you beat me to it 😸

I just opened #91. I am happy to close my PR, although I would suggest removing the TODO comments as I feel they are not needed

@fearoffish
Copy link
Author

Good point. I'll remove the TODO comments. I'm not sure if the comment about this issue is resolved though. Following the thread it looks like it, but this PR isn't the place to remove that.

@rparsonsbb
Copy link

Every coalescelist that returns only empty tuples will Error until 0.12.1 re: hashicorp/terraform#21370

temporary workaround is to provide a bogus [""] at the end of each coalescelist in outputs.tf

@den-is
Copy link
Contributor

den-is commented May 31, 2019

tested, in my prod, works great with additional fix mentioned by @rparsonsbb

@fearoffish
Copy link
Author

@rparsonsbb @den-is Thanks for that, I've added the fix.

@heisian
Copy link

heisian commented Jun 6, 2019

@antonbabenko can this get some attention?

@fearoffish I noticed the outputs from this module are lists within lists. i.e.,

Outputs:

id = [
  [
    "i-048620cxxx",
    "i-0e361f9bxxx",
    "i-0bbb8cexxx",
    "i-034792bxxx",
    "i-060f929xxx",
  ],
]

Is this intended? I modified the outputs file like so, so that all outputs are a non-nested list, i.e.:

Outputs:

id = [
  "i-048620cxxx",                                                                                                                                    
  "i-0e361f9bxxx",                                                                                                                                                    
  "i-0bbb8cexxx",                                                                                                                                    
  "i-034792bxxx",                                                                                                                                              
  "i-060f929xxx",                                                                                                                                                                                                                                                                                                      
]

To me, my modified version makes more sense, but I also just started terraforming in 0.12, so I don't have the full context of the original behavior of this module.

@antonbabenko antonbabenko mentioned this pull request Jun 6, 2019
@antonbabenko
Copy link
Member

Thanks, @fearoffish @den-is @rparsonsbb @heisian @yasn77 and everyone involved in one way or another!

v2.0.0 has been just released.

Remember to pin module version to be ~> v1.0 if you are using Terraform 0.11, and use ~> 2.0 if you are using Terraform 0.12.

Please give this release a try and open an issue if there is something wrong.

@heisian
Copy link

heisian commented Jun 6, 2019

works! thank you @antonbabenko !

@fearoffish
Copy link
Author

Thanks @antonbabenko!

@antonbabenko
Copy link
Member

You are welcome!

@Amdingo
Copy link

Amdingo commented Jun 6, 2019

Awesome works great thanks all!

@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.

7 participants