Skip to content

Conversation

@IBM-Deeksha
Copy link
Contributor

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

@IBM-Deeksha IBM-Deeksha marked this pull request as ready for review October 31, 2025 11:57
Summary: "Update Not Supported",
Detail: "The resource definition will be only be removed from the terraform statefile. This resource cannot be deleted from the backend. ",
}
diags = append(diags, warning)
Copy link
Collaborator

Choose a reason for hiding this comment

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

why do we remove in update also?
Then will not it show a new resource far every apply?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hkantare It won’t create a new resource on every apply because Terraform keeps the ID in state and our Read is a no-op, so subsequent applies see the resource as already existing and don’t call Create again.

}

func resourceIbmBackupRecoveryManagerCreateClusterUpgradesUpdate(context context.Context, d *schema.ResourceData, meta interface{}) diag.Diagnostics {
// This resource does not support a "delete" operation.
Copy link
Collaborator

Choose a reason for hiding this comment

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

same as above comment


# Syntax
<pre>
$ terraform import ibm_backup_recovery_manager_cancel_cluster_upgrades.backup_recovery_manager_cancel_cluster_upgrades &lt;id&gt;
Copy link
Collaborator

Choose a reason for hiding this comment

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

The ID is some time stamp , how will import helps the customer

Copy link
Collaborator

Choose a reason for hiding this comment

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

Same for all resource docs

Copy link
Contributor Author

@IBM-Deeksha IBM-Deeksha Nov 20, 2025

Choose a reason for hiding this comment

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

@hkantare
These 3 resources do not support import.
Have updated the same in doc for each resource.

Schema: map[string]*schema.Schema{
"cluster_identifiers": &schema.Schema{
Type: schema.TypeList,
Optional: true,
Copy link
Collaborator

Choose a reason for hiding this comment

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

why is it optional ?
We don't have any field with required?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hkantare
Have updated cluster_identifiers as required (same for the remaining resources)

```hcl
resource "ibm_backup_recovery_manager_create_cluster_upgrades" "backup_recovery_manager_create_cluster_upgrades_instance" {
}
```
Copy link
Collaborator

Choose a reason for hiding this comment

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

why we have mismatch between schema vs doc arguments

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hkantare
Updated the docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants