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

Allow graceful inconsistency management by TF when public_ips in reso… #386

Closed
wants to merge 1 commit into from

Conversation

outscale-toa
Copy link
Member

…urceOAPINatServiceRead() is empty

In resourceOAPINatServiceRead(), access to public_ips[0] isn't protected against empty list when the API can return an empty list in some edge cases. When public_ips is empty, setting public_ip_id to "" allows the TF refresh to succeed and the TF plan/apply to recreate the Nat Service with the correct public_ip_id.

…urceOAPINatServiceRead() is empty

In `resourceOAPINatServiceRead()`, access to `public_ips[0]` isn't protected against empty list when the API can return an empty list in some edge cases.
When `public_ips` is empty, setting `public_ip_id` to `""` allows the TF refresh to succeed and the TF plan/apply to recreate the Nat Service with the correct `public_ip_id`.
@outscale-toa outscale-toa temporarily deployed to test-us-east-2 October 12, 2023 09:46 — with GitHub Actions Inactive
@outscale-toa outscale-toa temporarily deployed to test-eu-west-2 October 12, 2023 09:46 — with GitHub Actions Inactive
@outscale-toa outscale-toa temporarily deployed to test-us-east-2 October 12, 2023 09:46 — with GitHub Actions Inactive
@outscale-toa outscale-toa temporarily deployed to test-eu-west-2 October 12, 2023 09:46 — with GitHub Actions Inactive
@outscale-toa outscale-toa deleted the fix_empty_public_ip_resp branch July 30, 2024 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants