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

fix(firewall_policy): replace ip address range with cidr range as valid input for threat_intelligence_allowlist #14340

Conversation

josh-barker
Copy link
Contributor

This PR address #14339 by:

  • removing IP address range as a valid input, as it's not supported
  • adding the CIDR range as a valid input

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @josh-barker - LGTM 🏗️

@katbyte katbyte merged commit c9d05a6 into hashicorp:main Nov 25, 2021
@github-actions github-actions bot added this to the v2.87.0 milestone Nov 25, 2021
katbyte added a commit that referenced this pull request Nov 25, 2021
@josh-barker josh-barker deleted the fix/firewall-policy-threat-allowed-ip-addresses branch November 25, 2021 22:44
@josh-barker
Copy link
Contributor Author

No worries @katbyte !

@github-actions
Copy link

This functionality has been released in v2.87.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants