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

Failing Make Install (wrong test inputs) #707

Closed
RishabhBhatnagar opened this issue Jul 24, 2020 · 5 comments
Closed

Failing Make Install (wrong test inputs) #707

RishabhBhatnagar opened this issue Jul 24, 2020 · 5 comments

Comments

@RishabhBhatnagar
Copy link

make install is failing due to failing test of sops/config/config_test.go. Lines 375 and 379 of the TestLoadConfigFileWithVaultDestinationRules are erroneous.

The test expects the output of conf.Destination.Path to have an http protocol but the function returns the output URL with https protocol which is causing the tests to fail.

@autrilla
Copy link
Contributor

This has indeed been broken for ages :( #576 attempted to fix it. For now, you can set the VAULT_ADDR env var to http://127.0.0.1:8200 to solve it.

@RishabhBhatnagar
Copy link
Author

Both the lines (375, 379) uses a config file with vault destination rules. If any URL is not specified, the VaultDestination.Path method of publish/vault.go uses a base URL supplied by getAddress() method of "github.com/hashicorp/vault/api" library which returns a base address with protocol of https.

For a quick fix, I've updated the tests to use https instead of http.

@RishabhBhatnagar
Copy link
Author

RishabhBhatnagar commented Jul 24, 2020

This has indeed been broken for ages :( #576 attempted to fix it. For now, you can set the VAULT_ADDR env var to http://127.0.0.1:8200 to solve it.

As I can see, #576 is associated with other things as well. Are we expecting that PR to be merged soon or should I create a new PR for fixing the current issue?

@autrilla
Copy link
Contributor

I don't think that PR is going to be merged any time soon, so it would be great if you create a new PR for fixing the issue.

@ajvb
Copy link
Contributor

ajvb commented Sep 2, 2020

Fixed with #731

@ajvb ajvb closed this as completed Sep 2, 2020
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

No branches or pull requests

3 participants