Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Issue with calculated counts when resources don't exist in state #2

Closed
pysysops opened this issue Jan 18, 2019 · 1 comment
Closed

Issue with calculated counts when resources don't exist in state #2

pysysops opened this issue Jan 18, 2019 · 1 comment

Comments

@pysysops
Copy link
Contributor

DNS example fails with:

* module.web.digitalocean_record.public_a: digitalocean_record.public_a: value of 'count' cannot be computed
* module.web.digitalocean_record.public_aaaa: digitalocean_record.public_aaaa: value of 'count' cannot be computed
* module.web.digitalocean_record.private_a: digitalocean_record.private_a: value of 'count' cannot be computed

On first run with a clean state.

Related to discussion in this issue: hashicorp/terraform#12570
pysysops added a commit that referenced this issue Jan 18, 2019
@pysysops
Remove private IPv6 related code, update DNS example.
6539341 
Fixes issue #1 - removes private IPv6 related code.

Fixes issue #2 - computed fields and counts in the DNS example.
@pysysops
Copy link
Contributor Author

Fixed with some decoupling of resources and updated DNS example README with caveat when using computed resources in count variable assignments.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pysysops