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

Remove viper from pkg/. #257

Merged
merged 1 commit into from Dec 2, 2021
Merged

Remove viper from pkg/. #257

merged 1 commit into from Dec 2, 2021

Conversation

mattmoor
Copy link
Member

@mattmoor mattmoor commented Dec 2, 2021

This change builds on #255. It moves the CA creating to the serve entrypoint, and attaches the appropriate CertificateAuthority to the request contexts. The same for the ct-log-url.

With this change, all of the viper logic lives under ./cmd and the logic in ./pkg receives its configurations through parameters (possible attached to ctx).

Signed-off-by: Matt Moore mattmoor@chainguard.dev

WIP until the base change lands.

Ticket Link

N/A

Release Note

NONE

@mattmoor
Copy link
Member Author

mattmoor commented Dec 2, 2021

@bobcallaway I think the next thing I'm going to chase after viper is sync.Once singletons since I think we have a bunch of those that seem gratuitous 🤔

This change moves the CA creating to the `serve` entrypoint, and attaches the appropriate `CertificateAuthority` to the request contexts.  The same for the `ct-log-url`.

With this change, all of the `viper` logic lives under `./cmd` and the logic in `./pkg` receives its configurations through parameters (possible attached to `ctx`).

Signed-off-by: Matt Moore <mattmoor@chainguard.dev>
@mattmoor mattmoor changed the title [WIP] Remove viper from pkg/. Remove viper from pkg/. Dec 2, 2021
@mattmoor mattmoor merged commit 3149b1d into sigstore:main Dec 2, 2021
@mattmoor mattmoor deleted the be-gone-viper branch December 2, 2021 03:19
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.

None yet

2 participants