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

Add gomod-override #34

Merged
merged 1 commit into from
Jan 23, 2019
Merged

Add gomod-override #34

merged 1 commit into from
Jan 23, 2019

Conversation

jen20
Copy link
Contributor

@jen20 jen20 commented Jan 23, 2019

gomod-override is analagous to govendor-override, except it works on go.mod files used with Go 1.11 modules instead of govendor.json files.

For now it has the following restrictions:

  • Only the first constraint in the template with gomod-override = true will be processed
  • Replace directives in the go.mod file are not honoured

This is sufficient to build a solvable set of dependency constraints for the Google Cloud Beta provider, which was the initial aim. It's anticipated that further work will be required over time.

A large amount of the code for parsing go.mod files is copy/pasted from the Go source tree, where it is marked internal.

gomod-override is analagous to govendor-override, except it works on go.mod
files used with Go 1.11 modules instead of govendor.json files.

For now it has the following restrictions:

- Only the first constraint in the template with `gomod-override = true` will be
  processed
- Replace directives in the go.mod file are not honoured

This is sufficient to build a solvable set of dependency constraints for the
Google Cloud Beta provider, which was the initial aim. It's anticipated that
further work will be required over time.
@jen20 jen20 merged commit 27d868c into master Jan 23, 2019
@pulumi-bot pulumi-bot deleted the jen20/gomod-override branch January 23, 2019 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants