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

Execute commands on netcup nodes. #196

Open
1 of 4 tasks
shtlrs opened this issue May 29, 2024 · 2 comments
Open
1 of 4 tasks

Execute commands on netcup nodes. #196

shtlrs opened this issue May 29, 2024 · 2 comments
Assignees
Labels

Comments

@shtlrs
Copy link
Member

shtlrs commented May 29, 2024

What should the command do?

The idea is us being able to execute specific actions on one of our NetCup boxes.

For this to happen, a King-Arthur user needs to be created on all of our boxes.
Then, using its own private key, KA can SSH into a particular box and execute a command from there.

I am not sure how to scope this in terms of commands/cogs, but i thought we could have a NetCup cog which contains 2 commands

  1. a raw command, to allow flexibility of using any command we want, and this needs to be granted to only a set of particular people. Ideally this command will prompt user for confirmation before using it.
  2. A fail2ban group/command that will mostly just allow unbanning IPs from a particular host.

All these commands will need to take the box name in param obviously.

APIs

  • CloudFlare
  • Kubernetes
  • Discord
  • Other

Who should be authorized to use this command?

DevOps

@shtlrs shtlrs added the command label May 29, 2024
@jchristgit jchristgit moved this from Up next to Backlog in Infrastructure Jul 24, 2024
@jchristgit
Copy link
Member

Do we still want this?

At present I can't think of commands we would run through this, except perhaps
fail2ban. But so far that has worked, plus the affected team members have surely
by now switched to password managers and no longer run into those issues.

@jb3
Copy link
Member

jb3 commented Sep 1, 2024

Fail2ban is the only thing that comes to mind right now also.

Potentially fetching info like things from "doveadm who" could be nice but isn't
a big deal.

I think it's fine to keep open but not prioritize implementation, it doesn't
hurt us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

3 participants