-
Notifications
You must be signed in to change notification settings - Fork 123
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
Incompatibility with latest version of Aliyungo provider #183
Comments
peczenyj
added a commit
to peczenyj/go-discover
that referenced
this issue
Sep 27, 2021
peczenyj
added a commit
to peczenyj/go-discover
that referenced
this issue
Sep 27, 2021
This reverts commit 986207c.
peczenyj
added a commit
to peczenyj/go-discover
that referenced
this issue
Sep 27, 2021
well... seems everyone is busy |
peczenyj
pushed a commit
to peczenyj/go-discover
that referenced
this issue
Dec 21, 2023
author Jeff Widman <[email protected]> 1621366525 -0700 committer Tiago Peczenyj <[email protected]> 1703171978 +0100 Update tencent version Tencent pulled the previous tag of their API and switched to `v1` starting here: https://github.com/TencentCloud/tencentcloud-sdk-go#%E9%80%9A%E8%BF%87go-get%E5%AE%89%E8%A3%85%E6%8E%A8%E8%8D%90 As a result, currently `go get -d` is complaining in downstream repos, breaking Dependabot (among other things). So this fixes that. Fix hashicorp#172. Update CI badge to CircleCI The old badge was travis, and we have not used travis in some time. update dependency fix incompatibity issue hashicorp#183 Revert "fix incompatibity issue hashicorp#183" This reverts commit 986207c. Revert "update dependency" This reverts commit bc42ce5. update dependency github.com/denverdino/aliyungo fix incompatibity issue hashicorp#183 go mod tidy Add AWS SessionToken Support (hashicorp#189) * add support for SessionToken in AWS credential resolver * add AWS AssumeRole configuration to AWS tests Fix "Config options" links Apply suggestions from code review Co-authored-by: Blake Covarrubias <[email protected]> deps: bump Azure/go-autorest to remove transitive jwt-go dependency with known vulnerability (hashicorp#174) update dependency github.com/denverdino/aliyungo Add AWS SessionToken Support (hashicorp#189) * add support for SessionToken in AWS credential resolver * add AWS AssumeRole configuration to AWS tests Fix "Config options" links Apply suggestions from code review Co-authored-by: Blake Covarrubias <[email protected]> Add AWS endpoint definition as an option (hashicorp#194) Signed-off-by: obeyler <[email protected]> Feature/aws ecs support (hashicorp#197) * Add service argument to aws provider, where service can be either ec2 or ecs (defaulting to ec2) * Add optional ecs_cluster and ecs_family arguments Update tencentcloud-sdk-go modules Dependencies are available as individual go modules now. [COMPLIANCE] Update MPL 2.0 LICENSE Adding workflow .github/actions/acctest/action.yml .github/actions/tf-install/action.yml .github/workflows/acceptance.yml SHA-pin all 3rd-party actions Restrict workflow permissions Add actionslint Add dependabot Add CODEOWNERS Remove CircleCI configuration Remove unused local actions Update migration enable scleway acceptance test add success job add success job fix copy pasta Result of tsccr-helper -pin-all-workflows . Fix CVEs Need at least go 1.16 for the golang.org/x/net fixes Update github action to use go 1.16 Some dependencies needed 1.17 Set miekg/dns to 1.1.50 Result of tsccr-helper -log-level=info -pin-all-workflows . Update README.md Update README.md Update README.md Update README.md update vendor github.com/denverdino/aliyungo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Aliyun provider does not compiles with latest version of package github.com/denverdino/aliyungo
go get returns this error
Incompatibilities:
go-discover/provider/aliyun/aliyun_discover.go
Line 74 in c573d69
and
https://github.com/denverdino/aliyungo/blob/4f11020c0bfbdc0f90604d18bfecfc524424a8a4/ecs/instances.go#L515
The text was updated successfully, but these errors were encountered: