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

Allow assignment of security_group_rule to multiple security_group objects #5800

Closed
cdorros opened this issue Mar 22, 2016 · 2 comments
Closed

Comments

@cdorros
Copy link

cdorros commented Mar 22, 2016

The work done here to create the new security_group_rule type is hugely appreciated - solved many cycle issues I was having:
#1620

It would be extremely useful to be able to assign security_group_rules to multiple security_groups, to allow for re-use. Additionally, inverting the assignment by allowing an array of security_group_rules to be defined in the security_group object, instead of the current behavior (assigning security_group ID to security_group_rule).

Title is related to #3525, but the content of that ticket is not what I'm after.

@cdorros cdorros changed the title Allow assignment security_group_rule to multiple security_group objects Allow assignment of security_group_rule to multiple security_group objects Mar 22, 2016
@phinze
Copy link
Contributor

phinze commented Mar 25, 2016

Hi @cdorros - definitely understand the desire to allow for security_group_rule reuse. Consolidating the conversation around this down in #2081. 👍

@phinze phinze closed this as completed Mar 25, 2016
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants