initialise config file

[berendsliedrecht]

We need an easy for the user to initialise the configuration file.

Proposed:

aries-cli config --initialise

this could also be aliased to:

aries-cli init

The first one would be more extensible, e.g. editing, but the first one is more user-friendly. Aliasing is the preferred solution here IMO.

[jl-animo]

Hm, I wonder whether we should do:

aries-cli config init

I think of --coolflag as modifiers to an action, not the action itself. Then, in future, we could have what you suggested:

• aries-cli config edit --editor /usr/bin/vim
• aries-cli -e my-env config set <key> <value>
• not that we want to, just illustrating action vs. modifier aries-cli config init --filetype ini

however, I think it'd be totally fine to alias aries-cli config init to aries-cli init and advertise users to rather just do aries-cli init when getting started.

[jl-animo]

Tangential thought: We could even remove the requirement that they run aries-cli init and just read a "default" config if they have not created one. however, I see this could add some friction down the road when they want to add a new environment and then we tell them about aries-cli init 🤔

[berendsliedrecht]

The default configuration has to be initialised to read from. We don't want to release the tool with a default linkt to our cloud agent because of load. So with a more proper release this init with our cloud agent will be removed.

[berendsliedrecht]

@jl-animo right now this is the api.

I agree strongly with your point on flags modifying the action and subcommands being the action. How would you structure this? we need a view, to simply log the default config file, and an initialise.

I assume you would like Aries-cli configuration initialise and Aries-cli configuration view ? If so, is this something you would like tho pick up?