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

Don't clobber other Galaxies' systemd units when managed by different Gravity config files #83

Merged
merged 3 commits into from Nov 7, 2022

Commits on Oct 28, 2022

  1. Only remove systemd configs that are "owned" by this Gravity.

    More specifically, ones that are related to a loaded Gravity config
    file. If you need to remove everything, you can use --clean --force.
    
    Related, update --force is obsolete on its own since the thing it
    originally did (always write PM configs regardless of whether the
    configstate changed) is meaningless now that there's no configstate: the
    PM configs are templated every time you run update, and are updated if
    they differ from what's on disk.
    
    The supervisor PM should probably switch to the systemd PM's logic here
    for --force. Tests for the desired behavior with --force and --update
    when multiple configs are used would also be good.
    natefoo committed Oct 28, 2022
    Configuration menu
    Copy the full SHA
    c968061 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8cb8c6f View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    4563d71 View commit details
    Browse the repository at this point in the history