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] Consider to employ ssh_auth.manage state within ssh_auth_sources #232

Open
mikhailmaximov opened this issue Mar 30, 2024 · 0 comments

Comments

@mikhailmaximov
Copy link

mikhailmaximov commented Mar 30, 2024

Is your feature request related to a problem?

Current implementation of ssh_auth_sources relies on explicit use of ssh_auth_sources.absent to remove obsolete SSH public keys from .ssh/authorized_keys file.
SaltStack v3000 introduced a new state ssh_auth.manage to explicitly enumerate keys that should be in .ssh/authorized_keys file

Describe the solution you'd like

There are two possible options:

  • switch ssh_auth_sources to use ssh_auth.manage state; or
  • introduce a new state ssh_auth_sources.manage as less disturbing solution

Describe alternatives you've considered

This is not critical, one can use Salt's ssh_auth.manage directly

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant