-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New Resource: azurerm_network_watcher_flow_log #5059
Conversation
* Update tests and move to network watcher tests. * Add docs.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with some minor comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few minor comments but this otherwise LGTM 👍
azurerm/resource_arm_hdinsight_interactive_query_cluster_test.go
Outdated
Show resolved
Hide resolved
Co-Authored-By: Tom Harvey <tombuildsstuff@users.noreply.github.com>
This has been released in version 1.40.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.40.0"
}
# ... other configuration ... |
Is there any particular reason to why it only supports version 1 flow logs? We have been using version 2 flow logs for a while, and was looking forward to this update where we could set flow logs through terraform only to find out that there is no option to choose flow logs version. Hope this can be implemented as well. |
@ThomasStubergh mind opening a new issue with more information/an example of a v1 vs v2 flow log? From our side this was an older PR re-opened since the API's been fixed, so it was likely omited since it wasn't historically available. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
continuation of #2262
fixes #1776