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

Throw a warning/error when target service doesn't exist #25

Open
rvem opened this issue May 11, 2023 · 0 comments
Open

Throw a warning/error when target service doesn't exist #25

rvem opened this issue May 11, 2023 · 0 comments

Comments

@rvem
Copy link
Member

rvem commented May 11, 2023

By default

vault-secrets.secrets.example = {};

Will create example-secrets.service and use it as a dependency for example.service. However, if example.service doesn't exist, vault-secrets will still create it. While the actual target service(s) will miss the example-secrets.service dependency.

IMO, vault-secrets should either throw a warning or an error at evaluation time in case some services from vaule-secrets.secrets.<name>.services don't exist in systemd.services.

karandit added a commit that referenced this issue May 11, 2023
Problem: the current snippet in README (still) contains an invalid
configuration (see [this](#25))

Solution: Replace mysecret with myservice
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

1 participant