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

No warnings about misconfiguration #10

Open
frederictobiasc opened this issue Jan 10, 2025 · 0 comments
Open

No warnings about misconfiguration #10

frederictobiasc opened this issue Jan 10, 2025 · 0 comments

Comments

@frederictobiasc
Copy link

frederictobiasc commented Jan 10, 2025

Hi!
I understand we cannot prevent users completely of creating invalid configurations. But consider the following case:

If preservation is configured to preserve a directory (say /etc/foo) that is part of a path managed by etc.environment (say etc.environment."foo/bar") this has potentially unintended results.

It's also a bit tricky, since configuration for etc.environment could be provided by any module (e.g. from nixpkgs) rather than being defined by the user creating the preservation configuration.

I think especially for etc.environment it would be nice if some kind of warning would be generated, if there is potential interference with the preservation configuration.

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