Skip to content
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

Bump go-discover to fix broken dep tree #10898

Merged
merged 2 commits into from
Sep 16, 2021
Merged

Bump go-discover to fix broken dep tree #10898

merged 2 commits into from
Sep 16, 2021

Conversation

jeffwidman
Copy link
Contributor

The previous version of go-discover pulled in a broken version of
tencentcloud-sdk-go, resulting in anything that runs go get -d
downstream breaking... ie, a dep on hashicorp consul will break
Dependabot (among other things).

I already fixed it in go-discover, so this just pulls in the update.

More details in
hashicorp/go-discover@657e803
and hashicorp/go-discover#172.

Unfortunately, it looks like pulling this in also forces a couple of k8s
packages to get updated. I did not manually bump these... they were the
outcome of running go mod tidy.

The previous version of `go-discover` pulled in a broken version of
`tencentcloud-sdk-go`, resulting in anything that runs `go get -d`
downstream breaking... ie, a dep on hashicorp consul will break
Dependabot (among other things).

I already fixed it in `go-discover`, so this just pulls in the update.

More details in
hashicorp/go-discover@657e803
and hashicorp/go-discover#172.

Unfortunately, it looks like pulling this in also forces a couple of k8s
packages to get updated. I did not manually bump these... they were the
outcome of running `go mod tidy`.
@vercel vercel bot temporarily deployed to Preview – consul August 23, 2021 18:47 Inactive
@jeffwidman jeffwidman changed the title Bump go-discover to fix broken dep tree Bump go-discover to fix broken dep tree Aug 23, 2021
@kisunji
Copy link
Contributor

kisunji commented Aug 24, 2021

Thanks for the diligence @jeffwidman !

Unfortunately as our CI shows, this version bump includes a transitive dependency update which has breaking API changes.
There is some ongoing work internally to be able to update our k8s versions, but this PR will be unable to be merged until that is resolved.

I'll check with the team and circle back to you

@jeffwidman
Copy link
Contributor Author

Unfortunately as our CI shows, this version bump includes a transitive dependency update which has breaking API changes.
There is some ongoing work internally to be able to update our k8s versions, but this PR will be unable to be merged until that is resolved.

Yep, as soon as I saw it was bumping k8s, I was like "I guess I'll be checking back in 6 months on this one...". Lots of work to stay updated with that ecosystem, so I completely understand and empathize.

@kisunji kisunji self-assigned this Aug 24, 2021
@kisunji kisunji added the dependencies Pull requests that update a dependency file label Aug 24, 2021
@hashicorp-cla
Copy link

hashicorp-cla commented Sep 9, 2021

CLA assistant check
All committers have signed the CLA.

@eculver
Copy link
Contributor

eculver commented Sep 14, 2021

So we're waiting on confirmation that this version is supported correct?

@kisunji
Copy link
Contributor

kisunji commented Sep 15, 2021

So we're waiting on confirmation that this version is supported correct?

I thought it would be a messy resolution but I found a similar PR that was closed last year: #9030. I don't think we ever followed through with the upgrade in our new releases.

I'll apply some of the changes in that PR (seems to be adding a few params) and see if that gets the CI building.

@vercel vercel bot temporarily deployed to Preview – consul September 16, 2021 19:14 Inactive
@kisunji kisunji added the pr/no-changelog PR does not need a corresponding .changelog entry label Sep 16, 2021
@kisunji kisunji merged commit 2dc62aa into hashicorp:main Sep 16, 2021
@kisunji
Copy link
Contributor

kisunji commented Sep 16, 2021

Managed to get this building! Thanks again @jeffwidman

@hc-github-team-consul-core
Copy link
Collaborator

🍒 If backport labels were added before merging, cherry-picking will start automatically.

To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/447727.

@jeffwidman
Copy link
Contributor Author

Awesome! Thanks @kisunji for pushing this across the line.

@jeffwidman jeffwidman deleted the bump-go-discover-past-broken-version branch September 16, 2021 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants