Skip to content
This repository was archived by the owner on Jun 5, 2020. It is now read-only.

Conversation

benpillet
Copy link
Contributor

Add a property for the associate_public_ip_address option for a launch configuration

Copy link
Contributor

@hunner hunner left a comment

Choose a reason for hiding this comment

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

Could you please rebase to fix conflicts and squash to a single commit? Thanks!

*Optional* A hint to specify the VPC. This is useful when detecting ambiguously named security groups that might exist in different VPCs, such as 'default'. This parameter is set at creation only; it is not affected by updates.

#####`associate_public_ip_address`
*Optional* One or more mappings that specify how block devices are exposed to the instance. For more information, see [Block Device Mapping](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) in the Amazon Elastic Compute Cloud User Guide. This parameter is set at creation only; it is not affected by updates.
Copy link
Contributor

Choose a reason for hiding this comment

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

The docs describe block devices; is that copy/paste?

def self.config_to_hash(region, config)
# It appears possible to get launch configurations manually to a state where
# they return the identifier of an invalid or a non-existent security groups
# puts "config_to_hash(#{config})"
Copy link
Contributor

Choose a reason for hiding this comment

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

Odd indentation.

end

end
def read_only_warning(value, property, should)
Copy link
Contributor

Choose a reason for hiding this comment

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

The module already has the ability for marking properties read-only; why this addition?

@prozach
Copy link
Contributor

prozach commented Feb 10, 2017

@benpillet Would you mind coming back to address the comments here please?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants