Update the tip for security groups #2254
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When users have dynamic ASG's feature enabled they don't need to
restart/restage their application for security group updates to take and
effect.
Thank you for contributing to the CF CLI! Please read the following:
If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
Does this PR modify CLI v6, CLI v7, or CLI v8?
v7, v8, v9
Description of the Change
TAS 2.13 introduces dynamic asgs feature which automatically updates security-groups for running and staging applications without the need for restart after security-groups were added/updated or removed.
Why Is This PR Valuable?
Users will see the new tip after they run security-groups commands like (
bind-security-group
,unbind-security-group
andupdate-security-group
) that their changes will be applied automatically if they have dynamic asgs enabled.Why Should This Be In Core?
Because it is currently in core and provides incorrect tip.
Applicable Issues
Original issue in cf-networking release
How Urgent Is The Change?
We need this to be released for 2.13 (code freeze February 21, 2022)