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

Update NetworkACL by replacement #80

Merged
merged 16 commits into from
Jan 8, 2016
Merged

Update NetworkACL by replacement #80

merged 16 commits into from
Jan 8, 2016

Conversation

Jc2k
Copy link
Member

@Jc2k Jc2k commented Jan 5, 2016

It's more efficient (in terms of API calls) and safe (in terms of database transaction like atomic switching) to create a network acl and update subnets to use it rather than modifying an existing one in place. This PR switched Network ACL to use this style of deployment, and includes serializer/diffing improvements to better handle the structure of the NetworkACL Rule type.

Todo:

  • Fix tests
  • Fix name of newly created acls...
  • Fix str() of network acl rule (including strification of protocol - 6 -> tcp etc)
  • Fix vpc.add_network_acl(port=23)
  • Fix vpc.add_network_acl(port_start=23, port_end=23)
  • It would be nice if the 'compound types' weren't resources

Jc2k added a commit that referenced this pull request Jan 8, 2016
Update NetworkACL by replacement
@Jc2k Jc2k merged commit 88bf94b into master Jan 8, 2016
@Jc2k Jc2k deleted the update_by_replacement branch January 8, 2016 11:33
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

1 participant