tests: use existing resources and test DA directly

[jor2]

Description

The code in https://github.com/terraform-ibm-modules/terraform-ibm-cloudpak-data is only a DA (no module). The DA contains a provider configuration and is not compatible with the for_each, count, and depends_on arguments, hence should not be consumed the way it is in the basic example. So we should remove the basic example and instead update the tests to directly test the DA code.

To do this, we will need to have code in the tests folder to provision the pre-req cluster (same way we do in other DA tests when working with existing resources).
I also notice the DA is not locked into exact provider versions. We should lock into an exact version to ensure consistency.

Release required?

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

Release notes content

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.

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀