feat: add direct endpoint support

[jor2]

Description

#1076

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]

@toddgiguere i am getting an error with the br-sao region direct endpoint which cos says it supports. Are we missing something in the tests?

TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │ Error: RequestError: send request failed
TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │ caused by: Put "https://s3.direct.br-sao.cloud-object-storage.appdomain.cloud/vsi-upg-afgunw-workload-bucket-jc4qze2w": dial tcp 161.26.0.96:443: i/o timeout
TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │ 
TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │   with module.vpc_landing_zone.module.landing_zone.ibm_cos_bucket.buckets["workload-bucket"],
TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │   on ../../cos.tf line 81, in resource "ibm_cos_bucket" "buckets":
TestRunUpgradeVsiExstention 2025-10-16T22:15:26Z logger.go:67: │   81: resource "ibm_cos_bucket" "buckets" {

[toddgiguere]

@jor2 Nothing that I can think of, and the COS bucket endpoint looks correct.

I do know that I will randomly see i/o timeouts like that on buckets across many regions which we think is a timing issue? I would try again just to be sure.

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[ocofaigh]

direct endpoint requires access to ibm cloud private network. So you would need to make sure the tests are running in schematics