Skip to content

Conversation

@daniel-butler-irl
Copy link
Contributor

@daniel-butler-irl daniel-butler-irl commented Nov 7, 2025

Description

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.

workspaceID string,
jobID string,
location string,
logger commonpkg.Logger,
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of passing logger should we use CloudInfoService.Logger ?

Copy link
Contributor

Choose a reason for hiding this comment

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

Many functions in cloudinfo/schematics.go that take logger as a parameter


// GetRefreshToken will use a previously established Authenticator to create a new IAM Token object,
// if existing is not valid, and return the refresh token propery from the token object.
func (svc *SchematicsTestService) GetRefreshToken() (string, error) {
Copy link
Contributor

Choose a reason for hiding this comment

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

@whoffler
Copy link
Contributor

whoffler commented Nov 10, 2025

schematics authenticates using the infoSvc.authenticator.RequestToken() which replaces the svc.ApiAuthenticator.RequestToken() call. They seem to be making the same call, could there be something in the order of calls that affects this?

We're getting:

image

Update:
Think I see the difference... we need to update the authenticator

svc.ApiAuthenticator = &core.IamAuthenticator{
		ApiKey: ibmcloudApiKey,
		ClientId:     "bx", // missing from cloudinfo authenticator
		ClientSecret: "bx", // missing from cloudinfo authenticator
	}

Update:

Tested update to cloudInfo authenticator adding ClientId and ClientSecret and have passing schematics tests

@daniel-butler-irl
Copy link
Contributor Author

/run pipeline

@daniel-butler-irl daniel-butler-irl merged commit bf50f18 into main Nov 11, 2025
1 check passed
@daniel-butler-irl daniel-butler-irl deleted the bob_migrate_schematics branch November 11, 2025 12:02
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.60.23 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants