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 REQUEST] Support for repo format DEB822 #66928

Open
ppoudrier-omnimed opened this issue Sep 26, 2024 · 1 comment
Open

[FEATURE REQUEST] Support for repo format DEB822 #66928

ppoudrier-omnimed opened this issue Sep 26, 2024 · 1 comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. needs-triage

Comments

@ppoudrier-omnimed
Copy link

Is your feature request related to a problem? Please describe.
Actually, when I use the following state, it always get executed.

suricata-repo:
  pkgrepo.managed:
    - ppa: oisf/suricata-stable

I digged deeper to find that the repo is never listed in salt 'host' pkg.list_repos
Please note that le ppa of suricata for Ubuntu 24.04 always return the deb822 format and if I try to force the use of keyserver and keyid, the key is invalid to apt

Describe the solution you'd like
I would like have a state that do not reinstall the repo each time so I can have a valid test=true to know if something need to be applied

Describe alternatives you've considered
I ended using file.managed

Additional context

  • Tested with salt version 3006.9 (Master and Minion)
  • Master on Ubuntu 20.04 and Minion on Ubuntu 24.04

Please Note
If this feature request would be considered a substantial change or addition, this should go through a SEP process here https://github.com/saltstack/salt-enhancement-proposals, instead of a feature request.

@ppoudrier-omnimed ppoudrier-omnimed added Feature new functionality including changes to functionality and code refactors, etc. needs-triage labels Sep 26, 2024
Copy link

welcome bot commented Sep 26, 2024

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant