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

Explicit validation of GCE region input. #146

Merged
merged 1 commit into from
Nov 8, 2018
Merged

Explicit validation of GCE region input. #146

merged 1 commit into from
Nov 8, 2018

Conversation

smarlowucf
Copy link
Collaborator

Region must be the full zone such as us-west1-a.

Without explicit validation an error can occur later in the process inside libcloud. This yields a cryptic error message which is hard to debug.

Region must be the full zone such as us-west1-a.
Copy link
Collaborator

@rjschwei rjschwei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval is conditional on the verification that ex_get_zone() is a dynamic list and not som ehard coded list in libcloud. If the latter we need to re-think this.

@smarlowucf
Copy link
Collaborator Author

Hardcoded lists are only EC2 issue since it has no endpoint for the info.

https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/gce.py#L7688

Sends request to GCE for zone info.

@smarlowucf smarlowucf merged commit 0a44887 into master Nov 8, 2018
@smarlowucf smarlowucf deleted the gce-zone branch November 8, 2018 02:14
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

Successfully merging this pull request may close these issues.

None yet

2 participants