-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix build command for version 2.x of AWS provider #39
base: main
Are you sure you want to change the base?
Conversation
Underlying issue: golang/go#51706
Thanks for the PR. Are you having issues installing AWS provider? |
Go 1.18 is where the error is thrown. Please see the link I placed in the commit message: |
@Junkern can you provide an update? Any reason this can't be merged? I honestly don't know how I'd resolve these failing tests. |
I had the same problem when installing
|
@et304383 sorry for the long delay. I am actually torn between the two decisions... on the one hand it is not a problem of this tool, but of the provider and |
@Junkern I agree. Maintaining this list going forward will be challenging as more bugs are introduced in newer versions of go, etc. I think the custom build command was a huge leap, but now it seems that we're going to rely more and more on that going forward. I'm almost thinking that it's time to make it (custom build command) a mandatory argument as there's no way you can keep this maintained going forward. Maybe coupling it with some kind of file structure that users could maintain that would define the build command for various providers/versions? A default location for this file, then users can edit once if a new issue arrises, and then move on. |
Underlying issue: golang/go#51706
What does this do / why do we need it?
This fixes the install of the AWS provider 2.x due to a bug in Go sys module
How this PR fixes the problem?
Updates the sys module before running the various build commands, only for the command used to compile the AWS provider
What should your reviewer look out for in this PR?
N/A
Check lists
Which issue(s) does this PR fix?
N/A