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

Add uninstall option and explain in documentation #41

Open
ozmium opened this issue Apr 9, 2018 · 2 comments
Open

Add uninstall option and explain in documentation #41

ozmium opened this issue Apr 9, 2018 · 2 comments

Comments

@ozmium
Copy link

ozmium commented Apr 9, 2018

Currently, there is no way to uninstall keymaker.

Please add this option and explain how to do it in the documentation.

It would also be helpful to list where the keymaker files are installed to (file paths).

@kislyuk
Copy link
Owner

kislyuk commented Apr 9, 2018

These are definitely good suggestions. For your reference, keymaker is intended for use in environments where you procedurally and idempotently generate and save AMIs, instead of managing them on an ad hoc basis (which is the only scenario in which you'd need such a command). I would encourage you to look into ways to build your AMIs and manage your instances automatically.

With that said, the listing of files is a low priority and easy item to do. The actual uninstall command is low priority and high complexity (figuring out a safe way to back out keymaker-induced changes from the sshd config is an open question for me).

PRs are welcome.

@quagly
Copy link

quagly commented Dec 19, 2018

Agree that with automation of keymaker setup this is a non-issue. An alternative to baking keymaker into an AMI is to automate keymaker installation from a vanilla AMI, for example using cloudformation. Then when you don't want keymaker just remove the automation or just use a vanilla AMI

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

No branches or pull requests

3 participants