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

Appending routes cause recreation of routes and rules #30

Open
nitrocode opened this issue Jan 27, 2022 · 0 comments
Open

Appending routes cause recreation of routes and rules #30

nitrocode opened this issue Jan 27, 2022 · 0 comments

Comments

@nitrocode
Copy link
Member

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Slack Community

Describe the Feature

Appending routes cause recreation of routes leading to failed terraform applies due to many unnecessary routing changes.

If we use a map for both var.authorization_rules and var.additional_routes, then we can use a for_each instead of count for auth rules and vpn routes and make the key something like {stage}-{cidr} or similar

count = local.enabled ? length(var.authorization_rules) : 0

count = local.enabled ? length(var.additional_routes) : 0

then we would be able to append routes and rules, avoid unnecessary deletions, and reduce the likelihood of the following error.

│ Error: error deleting client VPN route "cvpn-endpoint-snip,subnet-snip,10.66.0.0/15": timeout while waiting for resource to be gone (last state: 'deleting', timeout: 1m0s)

│ Error: error creating client VPN route "cvpn-endpoint-snip,subnet-snip,10.68.0.0/15": ConcurrentMutationLimitExceeded: Cannot initiate another change for this endpoint at this time. Please try again later.
jurgenweber added a commit to jurgenweber/terraform-aws-ec2-client-vpn that referenced this issue Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant