Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Update go mod tidy (and fix for Azure/go-autorest & azure-sdk-for-go) #451

Merged
merged 1 commit into from
Sep 20, 2019

Conversation

daxmc99
Copy link
Contributor

@daxmc99 daxmc99 commented Sep 16, 2019

This is a temporary fix similar to that from coredns/coredns#3258

See coredns/coredns#3209 (comment) for the previous issues, also see Azure/go-autorest#414 for some further background.
Basically go mod has some issue when multiple tags exist (as main module and submodule) within the same repo. That was fixed in go-autorest very recently, though azure-sdk-for-go has not been fully updated yet.
This fix is a temporarily one with replace fix. Once azure-sdk-for-go is updated then we could drop the replace fix

This fix can be dropped once our dependencies are updated to a more recent version of the Azure/go-autorest
Note: This only occurs with go mod tidy on go1.13

@ibuildthecloud
Copy link
Contributor

Hmm, still conflicting/faliing

We have dependencies that depend on pre-module versions of
the azure go-autorest client. This causes ambiguous import
errors in go1.13. We should remove the replace directive when
we upgrade our dependencies.
Copy link
Contributor

@StrongMonkey StrongMonkey left a comment

Choose a reason for hiding this comment

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

LGTM, If we are switching to 1.13 this should be helpful. (This pr is to solve the issue that you can't run go mod tidy on 1.13)

@ibuildthecloud ibuildthecloud merged commit 9150655 into rancher:master Sep 20, 2019
@daxmc99 daxmc99 deleted the gomod branch September 20, 2019 03:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants