You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
locked and limited conversation to collaborators
Apr 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: