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: saved configuration #30

Open
mcg1969 opened this issue Aug 11, 2019 · 0 comments
Open

Feature: saved configuration #30

mcg1969 opened this issue Aug 11, 2019 · 0 comments

Comments

@mcg1969
Copy link
Collaborator

mcg1969 commented Aug 11, 2019

As ae5-tools gets more and more complex, there likely will arise a greater number of configuration options, some of which may benefit from having saved defaults. This is a call for someone to deliver a mechanism for saving configuration values to disk.

Let's talk about hostname for a moment. This typically feels like it has a saved defaults because of how the latest accessed session is recovered. But it might nevertheless be useful for a default hostname to be hardcodable (is that a word)? For instance, if someone regularly interacts with serverA and occasionally interacts with serverB, it might be useful to nevertheless force serverA to be the default every time, even if the last command was executed on serverB.

For username and admin_username: If a saved config mechanism saves these, they should likely be done on a per-host basis.

Some options may only be relevant to certain commands. I wonder if there is a convenient mechanism for specifying defaults those. Perhaps some sort of tree mechanism; e.g., project.list.format.?

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

1 participant