feat: new scc code to retrieve latest scc profile version

jor2 commented 2 months ago

Description

The logic here assumes that each profile name will always have a latest = true value. However we have seen the SCC team change the profile names, meaning we can no longer rely on that logic.

Implementing our own logic to determine the latest version of a profile.

lookup all versions of a profile sort them return the latest That way we ensure there is ALWAYS a latest version for every profile name

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

update SCC logic around determining latest profile version

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 commented 1 month ago

/run pipeline

jor2 commented 1 month ago

/run pipeline

jor2 commented 1 month ago

/run pipeline

terraform-ibm-modules-ops commented 1 month ago

:tada: This issue has been resolved in version 1.6.4 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

terraform-ibm-modules / terraform-ibm-scc