oli: Introduce command oli config

[knight42]

Related: #422 RFC

oli config is responsible for managing user configuration files. It consists of several subcommands:

• oli config set-profile: update or add a profile in the current config
  • Usage: oli config set-profile <name> <type> [options]..., e.g:
  • oli config set-profile mys3 s3 bucket=foo access_key_id=bar
• oli config delete-profile: delete the given profile from the config
  • Usage: oli config delete-profile <name>
• oli config edit: edit the config file from the default editor
  • Usage: oli config edit
  • It will open the editor defined by your OLI_EDITOR environment variable, or fall back to 'vi' for Linux or 'notepad' for Windows.
• oli config view: print out the current config

[Xuanwo]

I prefer to add this subcommand after all others have been added.

[suyanhanx]

• oli config add-profile: add a profile to the current config

How about using set to express simpler semantics? Then It can both represent add and override.

[knight42]

I prefer to add this subcommand after all others have been added.

@Xuanwo May I know the reason? With this command, I think users can edit/update config file more conveniently.

How about using set to express simpler semantics? Then It can both represent add and override.

@suyanhanx A good idea! I think the command name could be set-profile, as the config file might have options other than profiles, as the RFC said:

• OIL_COLOR=always
• OIL_CONCURRENCY=16

[suyanhanx]

A good idea! I think the command name could be set-profile, as the config file might have options other than profiles, as the RFC said:

Yes. That's what I mean.

[Xuanwo]

With this command, I think users can edit/update config file more conveniently.

You are right. But users can still use oli without config support. And users nearly use cli to change config. So I think it's less important than other features.

It's a feature that good to have instead of must have.

[Xuanwo]

I don't think it's a good idea to add oli config at the moment. Let's reconsider this matter when we receive feature requests from actual users.