Skip to content

allow specifying standard as a domain in ex_associate_address_with_node#335

Closed
zerthimon wants to merge 1 commit intoapache:trunkfrom
zerthimon:use_standard_domain
Closed

allow specifying standard as a domain in ex_associate_address_with_node#335
zerthimon wants to merge 1 commit intoapache:trunkfrom
zerthimon:use_standard_domain

Conversation

@zerthimon
Copy link
Contributor

AWS uses "domain" field to distinguish between EIPs allocated for Classic EC2 ('standard') and EIPs allocated for VPC (value 'vpc')

domain
Indicates whether this Elastic IP address is for use with instances in EC2-Classic (standard) or instances in a VPC (vpc).
Type: xsd:string
Valid values: standard | vpc

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-ItemType-DescribeAddressesResponseItemType.html

The method ex_allocate_address() also uses 'standard' and 'vpc' as allowed parameters.

This patch adds 'standard' as a value to domain parameter.
None is left for backward compatibility.

@zerthimon
Copy link
Contributor Author

Something went wrong with the travis tests. Is there a way to tell it to recheck ?

@allardhoeve
Copy link
Contributor

Yes, you can push an empty commit to the branch by using git commit --allow-empty. Ugly trick, I know, but it can be done. Make sure to merge trunk into this branch, there were loads of CI fixes lately.

@allardhoeve
Copy link
Contributor

Looks good to me, but get the tests to work first, please.

@asfgit asfgit closed this in 0e7454d Nov 23, 2015
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.

2 participants