fix: workaround group on restore

[shemau]

Description

Add a work around to remove the group block when restoring from a backup.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Avoid defining the host_flavor during restore operations.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[shemau]

/run pipeline

[alexhemard]

Seems this may prevent scaling after restoring from a backup?

[shemau]

The restore from backup is a one time operation.

In order to scale after restoring from backup, the process should (must) pass null in the backup_crn. This would restore the group block (per previous behaviour).

[shemau]

make run-tests-local RUN=TestRunRestoredDBExample

was run locally and passed. This was done to cover the backup/restore test which does not run as part of the PR validation.

[ocofaigh]

As per ICD team, we need to update the timeout value for update. They suggest this:

timeouts {
    create = "120m"
    update = "120m"
    delete = "15m"
  }

[shemau]

/run pipeline

[shemau]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.17.10 🎉

The release is available on:

• GitHub release
• v3.17.10

Your semantic-release bot 📦🚀