-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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_replication_recovery_plan
;New Data Source: azurerm_site_recovery_replication_recovery_plan
#19940
New Resource: azurerm_site_recovery_replication_recovery_plan
;New Data Source: azurerm_site_recovery_replication_recovery_plan
#19940
Conversation
…y_replication_recovery_plan`
azurerm_site_recovery_replication_recovery_plan
azurerm_site_recovery_replication_recovery_plan
azurerm_site_recovery_replication_recovery_plan
azurerm_site_recovery_replication_recovery_plan
, New Data Source: azurerm_site_recovery_replication_recovery_plan
close and will reopen when the test finish |
azurerm_site_recovery_replication_recovery_plan
, New Data Source: azurerm_site_recovery_replication_recovery_plan
azurerm_site_recovery_replication_recovery_plan
;New Data Source: azurerm_site_recovery_replication_recovery_plan
website/docs/r/site_recovery_replication_recovery_plan.html.markdown
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Outdated
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Show resolved
Hide resolved
internal/services/recoveryservices/site_recovery_replication_recovery_plan_resource.go
Outdated
Show resolved
Hide resolved
|
||
* `target_recovery_fabric_id` - (Required) ID of target fabric to recover. Changing this forces a new Replication Plan to be created. | ||
|
||
* `recovery_group` - (Required) Three or more `recovery_group` block. At least one `recovery_group` for every `group_type` needed. |
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.
Not quite understand the second sentence. group_type
is one element of recovery_group
, so each recovery_group
has a group_type
?
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.
yes, and there should be at least three recovery_group
Maybe we can make recovery_group
a computed one to avoid this?
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.
Can it be computed
? Isn't recovery_group
a configurable property?
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.
I remember there is some trouble as it's typeSet
.. if I set it to computed
there might be a diff, let me give it a try.
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.
The default hash for Set
will ignore the computed
properties. The problem is: if this property is configurable by users, it should not be set as computed
?
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.
it's configurable and if the users do not configure it, it will also be generated by service.
My problem is the block, I want to set it to computed
then the users have no need to add blocks they do not use in their config file.
while in this situation, it get response with 3 recovery_group
, but only one in the config file, then there will be a diff.
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.
Souds like a backend problem. Normally, the backend should not change the configuration sent by the frontend.
website/docs/r/site_recovery_replication_recovery_plan.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/r/site_recovery_replication_recovery_plan.html.markdown
Outdated
Show resolved
Hide resolved
remove `vault_name` & `resource_group_name` and use `recovery_vault_id`
…changes to computed
convert to draft to re run tests |
new test result
|
Hello, the azurerm recovery plan still not supported in the new version (3.39.1) ? |
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.41.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
data source