-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
Support new Ohio region (us-east-2) #313
Comments
Yeah, we have that in place to try and make it more nice and explicit if an invalid region gets passed in (unfortunately it means we need to add new regions as they appear). I think it just needs to be in this list if you'd like to help us update: https://github.com/fog/fog-aws/blob/master/lib/fog/aws.rb#L228 (you could also monkey-patch this method if you need it immediately). Thanks! |
Monkey-patching gets past the first issue easily but the real problem is |
Ah, yeah that is problematic. Looks like it might be available via list hosted zones? http://docs.aws.amazon.com/Route53/latest/APIReference/API_ListHostedZones.html |
@mark-greene and @geemus
|
I'll check it out. I found the IDs (http://docs.aws.amazon.com/general/latest/gr/rande.html#elb_region) for ELBs. DNS works well for Instances and ELBs in any region other than Ohio. I haven't been able to successfully monkey-patch .rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/excon-0.54.0/lib/excon/middlewares/expects.rb:7:in `response_call': InvalidChangeBatch => "" is not a valid hosted zone id. is not a valid encrypted identifier (Fog::DNS::AWS::Error) I can make it work by overriding the default behavior but I have to add region specific code in my scripts. Normally I do not have to hardcode "HostedZoneId".
|
@mark-greene got it. If you share the monkey-patch attempt code I might be able to figure out what is going awry. |
Just tried the simple patch of
And I use it:
Doesn't work in Ohio unless I add |
Are you sure the entry you are working on is dualstack? Otherwise there is a second set of ids in that file here:
|
Yes, It's dualstack and I've tried both. I haven't spent any more time trying to figure out the patch and am just living with the alias_target workaround. When I get the chance (If it's not been addressed) I try to figure out the patch. |
Sounds good, thanks for the update. |
I think this PR has the required changes , if we can close this @geemus and @mark-greene |
@chanakyad-cuelogic good catch, I believe you are correct. |
I get the following when I try to access the Ohio region:
.../.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/fog-aws-0.12.0/lib/fog/aws.rb:234:in validate_region!': Unknown region: "us-east-2" (ArgumentError)
The text was updated successfully, but these errors were encountered: