-
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_site_recovery_hyperv_replication_policy
#20454
New Resource:azurerm_site_recovery_hyperv_replication_policy
#20454
Conversation
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.
Thanks @ziyeqf, left some comments in-line, once those are fixed up we can have another look and get this merged!
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource_test.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource_test.go
Outdated
Show resolved
Hide resolved
website/docs/r/site_recovery_replication_policy_hyperv.html.markdown
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_policy_hyperv_resource.go
Outdated
Show resolved
Hide resolved
website/docs/r/site_recovery_replication_policy_hyperv.html.markdown
Outdated
Show resolved
Hide resolved
azurerm_site_recovery_replication_policy_hyperv
azurerm_site_recovery_hyperv_replication_policy
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.
Test are failing..
------- Stdout: -------
=== RUN TestAccSiteRecoveryReplicationPolicyHyperV_basic
=== PAUSE TestAccSiteRecoveryReplicationPolicyHyperV_basic
=== CONT TestAccSiteRecoveryReplicationPolicyHyperV_basic
testcase.go:110: Step 1/2 error: Error running pre-apply refresh: exit status 1
Error: Missing required argument
on terraform_plugin_test.tf line 31, in resource "azurerm_site_recovery_hyperv_replication_policy" "test":
31: resource "azurerm_site_recovery_hyperv_replication_policy" "test" {
The argument "recovery_vault_id" is required, but no definition was found.
Error: Unsupported argument
on terraform_plugin_test.tf line 32, in resource "azurerm_site_recovery_hyperv_replication_policy" "test":
32: resource_group_name = azurerm_resource_group.test.name
An argument named "resource_group_name" is not expected here.
Error: Unsupported argument
on terraform_plugin_test.tf line 33, in resource "azurerm_site_recovery_hyperv_replication_policy" "test":
33: recovery_vault_name = azurerm_recovery_services_vault.test.name
An argument named "recovery_vault_name" is not expected here.
--- FAIL: TestAccSiteRecoveryReplicationPolicyHyperV_basic (2.37s)
FAIL
@katbyte sorry for that, forgot to update test case... test after udpate:
|
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.
Thanks @ziyeqf LGTM 🍀
This functionality has been released in v3.45.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! |
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. |
test