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

Edit digital ocean port range and ordering to suppress diff #98

Merged
merged 1 commit into from
Jan 17, 2018

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Jan 16, 2018

  • Change port range from keyword "all" to "1-65535", which is the
    same but with digitalocean provider 0.1.3 doesn't produce a diff
  • Rearrange egress firewall rules to order the Digtial Ocean API
    and provider returns. In current testing, this fixes the last diff
    that was present on terraform plan.

With digitalocean provider 0.1.3 and the module at this commit, terraform plan seems to show no diff. This could change in future as it relies on some ordering and conventions on the Digital Ocean API side, but it should fix #3.

Note: Its odd to specify ports for ICMP, but it seems to be the only way to satisfy the Terraform provider, which doesn't understand ICMP concepts. The Digital Ocean API just ignores the ICMP port value, correctly.

* Change port range from keyword "all" to "1-65535", which is the
same but with digitalocean provider 0.1.3 doesn't produce a diff
* Rearrange egress firewall rules to order the Digtial Ocean API
and provider returns. In current testing, this fixes the last diff
that was present on `terraform plan`.
@dghubble dghubble merged commit ef18f19 into master Jan 17, 2018
@dghubble dghubble deleted the do-port-range branch January 17, 2018 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terraform always reports firewall changes are needed
1 participant