-
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_vmware_replication_policy_association
#21389
New Resource: azurerm_site_recovery_vmware_replication_policy_association
#21389
Conversation
Hi @ziyeqf - Can you expand on the detail for the reason for this new association resource? Specifically expand on what the "further actions" are? |
Hi @jackofallops , I'd like to.
|
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 🚎
This functionality has been released in v3.58.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. |
It a bit strange to associate a policy (which is already in the same vault) to the vault, but it's needed to do the association to do further actions...
To run the test, it requires a VMWare machine connected to the Recovery Services Vault. It could not be deployed automatically in acctest. So, it needs to deploy one and provide the resource id in environment variables.
Test