SG Rule parameter

[Z3r0Sum]

It looks like there's a PR still open that is a much more robust enhancement (PR #32), but I think a hotfix is in order for being able to append SGs.

https://github.com/hudl/Tyr/blob/master/tyr/servers/server.py#L211

cc @jessehudl @citruspi - thoughts? I can craft something up.

[jessehudl]

👍 Would be great since classic instances can't be changed after launching.

[citruspi]

but I think a hotfix is in order for being able to append SGs.

What exactly are you looking for? To be able to have a set of "base" security group and then have additional, user-specifed security groups appended to that list?

classic instances can't be changes after launching.

In what way? The addition of security groups? That applies to all instances, not just classic ones. The primary difference between security groups on classic and VPC instances is that modifying the rules of a security group attached to a VPC instance doesn't cause network blips.

[jessehudl]

In what way? The addition of security groups? That applies to all instances, not just classic ones. The primary difference between security groups on classic and VPC instances is that modifying the rules of a security group attached to a VPC instance doesn't cause network blips.

Going by this answer here - http://serverfault.com/a/565852

this currently only applies to VPC instances. the security groups that a non-VPC instance belong to are fixed / immutable and are set when it's first launched. the only way to change them is to create a bundle from the existing instance and re-launch a new instance using the bundled ami. – ives Apr 9 '14 at 21:36

[citruspi]

Oh damn, I wasn't aware of that. Thanks for letting me know.