add option to configure destination cidr in egress firewall rules #265
+14
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d updated doc page accordingly
… ensure the new feature is optional and fully backward-compatible
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR introduces support for configuring a destination network in outgoing firewall rules, a feature introduced in API v4.10. The change is backward-compatible and not a breaking change, allowing users to optionally specify
dest_cidr_listin their configuration.References
API: https://cloudstack.apache.org/api/apidocs-4.22/apis/createEgressFirewallRule.html
Changes
Added
dest_cidr_listoption to the rules block ofcloudstack_egress_firewalland updated the documentation page accordingly.cloudstack/resource_cloudstack_egress_firewall.gowebsite/docs/r/egress_firewall.html.markdown