fix: AWS workaround #6
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deploying on AWS intermittently fails with i/o timeouts as the Juju Terraform provider returns inaccessible local IP addresses in the list of API controllers. See: juju/terraform-provider-juju#573
This PR contains three potential workarounds. Each determine if Juju's current cloud is 'aws' and set controller addresses to the non-local endpoint(s) if so. Details below:
Draft 1: Bash+regex in the
justfile.Draft 2: Python+JSON parsing in the
justfile(incomplete - does not run).Draft 3: Standalone
get_controller_addresses.pyscript used as an external data source inmain.tf.To graduate from draft status, a better check would be needed for invalid IPs (currently IPs starting
172and252are considered invalid), and error handling improvements.I'm opening this PR for comments - the plan is to look at the Terraform provider issue but thoughts on polishing one of these as a workaround in the meantime?