0

I have two internal projects.

Project1 - go.mod file

go github.com/company/project1
 
go 1.16

require github.com/company/project2 v1.1.0 // indirect

Project2 - go.mod file

go github.com/company/project2
 
go 1.16

Project1 is dependent on Project2 based on the above go.mod file.

When Project2 moves across multiple environments it needs to be dependent upon different version of Project1.
For instance, based on environment variable:

  • If ENVIRONMENT = LOAD

    Project1 depends on 1.1.0-<ENVIRONMENT> version of Project2

  • If ENVIRONMENT = TEST

    Project1 depends on 1.1.0-<ENVIRONMENT>.<DATE> version of Project2

Can this be done dynamically without modifying the go.mod file everytime ?

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
googytech
  • 479
  • 4
  • 7
  • 18

1 Answers1

1

Can this be done dynamically without modifying the go.mod file everytime ?

Not that I know of: your deployment process should include a go mod replace (as seen here) in order to update the project2 dependency, depending on the current deployment environment.

If that deployment involves a git clone, then you might consider content filter driver (illustrated here) to do that change automatically on checkout.

But if this is done through Go, then a go mod replace is better.

Note: issue 27824 (go.mod: using environment variable for replacement) was closed in 2019, because of implementation complexity.
Issue 33586 (go.mod: support ~ in replace statements) is still opened.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • That's right. The go mod replace is a pretty straightforward tool without any bells and whistles to handle any conditional logic. – googytech May 15 '21 at 11:46
  • Agreed. Hence my proposition to wrap that command in a script which will hosts the conditional logic – VonC May 15 '21 at 12:15