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

[Feature]: Support for dry-run #2641

Open
k0ste opened this issue May 13, 2024 · 0 comments
Open

[Feature]: Support for dry-run #2641

k0ste opened this issue May 13, 2024 · 0 comments

Comments

@k0ste
Copy link
Contributor

k0ste commented May 13, 2024

Motivation

It will be nice to have ability for a dry-run configuration

With a --dry-run option is possible to verify the config before restart application
How this should work:

[root@host]# oauth2-proxy --config /etc/oauth2-proxy/oauth2-proxy.conf --dry-run
[2024/05/13 19:47:00] [main.go:52] invalid configuration:
  cookie_secret must be 16, 24, or 32 bytes to create an AES cipher, but is 28 bytes

Exit code should be not zero

As we can see, if administrator, or orchestrator tool restart the application, the service goes down. With dry-run feature, config may be validated before application restart


Examples of application that already implemented dry-run feature:

  • sshd -T -f %s
  • keepalived -t -f %s
  • nginx -t -c %s

Possible solution

No response

Provider

None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant