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

accessing count directly in an output should is OK #16866

Merged
merged 1 commit into from
Dec 7, 2017

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Dec 7, 2017

There should be no warning when accessing a resource's count value
directly in an output.

Fixes #16864

There should be no warning when accessing a resource's count value
directly in an output.
@jbardin jbardin merged commit 62eb5ba into master Dec 7, 2017
@jbardin jbardin deleted the jbardin/count-splat-warning branch February 5, 2018 14:24
@ghost
Copy link

ghost commented Apr 4, 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 4, 2020
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.

Must use splat syntax to access aws_instance.instance attribute "count"
2 participants