- 
                Notifications
    
You must be signed in to change notification settings  - Fork 36
 
feat: add direct endpoint support #1077
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
           /run pipeline  | 
    
    
      
        3 similar comments
      
    
  
    | 
           /run pipeline  | 
    
| 
           /run pipeline  | 
    
| 
           /run pipeline  | 
    
| 
           @toddgiguere i am getting an error with the  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" { | 
    
| 
           @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.  | 
    
| 
           /run pipeline  | 
    
    
      
        2 similar comments
      
    
  
    | 
           /run pipeline  | 
    
| 
           /run pipeline  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
direct endpoint requires access to ibm cloud private network. So you would need to make sure the tests are running in schematics
| 
           /run pipeline  | 
    
| 
           /run pipeline  | 
    
| 
           /run pipeline  | 
    
| 
           🎉 This PR is included in version 8.11.0 🎉 The release is available on: 
 Your semantic-release bot 📦🚀  | 
    
Description
#1076
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers