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

Can't use go-config beyond version 0.7.0 #15

Open
etsauer opened this issue Feb 20, 2019 · 2 comments
Open

Can't use go-config beyond version 0.7.0 #15

etsauer opened this issue Feb 20, 2019 · 2 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@etsauer
Copy link
Collaborator

etsauer commented Feb 20, 2019

Description of Issue

After go-config v0.7.0, our operator breaks on startup citing that there is no provider configured.

How to Reproduce

Update the following constraint in Gopkg.toml from 0.7.0 to any later release:

[[constraint]]
  name = "github.com/micro/go-config"
  version = "0.7.0"

Install dependencies and start operator:

dep ensure
operator-sdk up local

Expected result

Operator starts successfully

Actual Result

panic: There was a problem detecting which provider to configure. 
	Provider kind `` is invalid. 
{"provider":{"kind":""},"general":{"annotations":{"status":"","status-reason":"","expiry":"","format":""}}}

goroutine 1 [running]:
github.com/redhat-cop/cert-operator/pkg/stub.NewHandler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/home/esauer/go/src/github.com/redhat-cop/cert-operator/pkg/stub/handler.go:32 +0x30e
main.main()
	/home/esauer/go/src/github.com/redhat-cop/cert-operator/cmd/cert-operator/main.go:33 +0x177
exit status 2
Error: failed to run operator locally: exit status 1
@etsauer etsauer added good first issue Good for newcomers bug Something isn't working labels Feb 20, 2019
@AdlerFleurant
Copy link

The version of go-config being used at this point is v1.1.0. Shouldn't we close this issue now? @etsauer

@etsauer
Copy link
Collaborator Author

etsauer commented Jul 10, 2019

@AdlerFleurant yes we can close, but can you first add a reference to the PR that resolved it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants