This PR reverts #38 -- depending on the storage package of grafeas-elasticsearch in Rode causes us to pull in a copy of Grafeas; which registers its protobuf declarations into the global registry and prints a bunch of warnings at app start:
[rode] 2021/02/18 17:22:07 WARNING: proto: message grafeas.v1beta1.Occurrence is already registered
[rode] A future release will panic on registration conflicts. See:
[rode] https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict
The only way I can think to get around that would be to refactor grafeas-elasticsearch and extract some of the components into their own package that doesn't reference Grafeas. That would be a bigger effort than just duplicating the types for now.
Also in the process of releasing those changes, the pipeline publish action failed trying to build for Apple ARM, because goreleaser recently added support. This downgrades the version of goreleaser until they release a fix for Go 1.15.
This PR reverts #38 -- depending on the
storagepackage ofgrafeas-elasticsearchin Rode causes us to pull in a copy of Grafeas; which registers its protobuf declarations into the global registry and prints a bunch of warnings at app start:The only way I can think to get around that would be to refactor
grafeas-elasticsearchand extract some of the components into their own package that doesn't reference Grafeas. That would be a bigger effort than just duplicating the types for now.Also in the process of releasing those changes, the pipeline publish action failed trying to build for Apple ARM, because goreleaser recently added support. This downgrades the version of goreleaser until they release a fix for Go 1.15.