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

[OPS-1402] Add warning about missing systemd restart policy #68

Merged
merged 1 commit into from
Jan 15, 2024

Conversation

Sereja313
Copy link
Member

Problem: We want to be notified that restart setup is needed when developing/testing/deploying a new module.

Solution: Add warning about missing systemd restart policy.

Description of changes

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Priorities

Add a 👍 reaction to pull requests you find important.

"acme-"
"mdmonitor"
"iodined"
"copr-cli"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think that's not an actual service and just a leftover that is relevant to serokell/vault-secrets#25 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh really, thank you

@@ -0,0 +1,1167 @@
3proxy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to quickly generate this list?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disregard, found an answer below 😅

Copy link
Member

@rvem rvem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Problem: We want to be notified that restart setup is needed when
developing/testing/deploying a new module.

Solution: Add warning about missing systemd restart policy.
@Sereja313 Sereja313 force-pushed the sereja/OPS-1402-restart-policy-warning branch from 40e6a45 to d42f159 Compare January 15, 2024 09:13
@Sereja313 Sereja313 merged commit f724378 into master Jan 15, 2024
4 of 5 checks passed
@delete-merged-branch delete-merged-branch bot deleted the sereja/OPS-1402-restart-policy-warning branch January 15, 2024 09:16
rvem pushed a commit that referenced this pull request Apr 30, 2024
Problem: We want to be notified that restart setup is needed when
developing/testing/deploying a new module.

Solution: Add warning about missing systemd restart policy.
rvem pushed a commit that referenced this pull request Sep 17, 2024
Problem: We want to be notified that restart setup is needed when
developing/testing/deploying a new module.

Solution: Add warning about missing systemd restart policy.
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.

2 participants