doc: miniojob doc

[jiuker]

[miniojob doc](doc: miniojob doc)

[shtripat]

LGTM

[pjuarezd]

@ravindk89 @feorlen would you mind checking on this please?

[ravindk89]

Sure thing!

[harshavardhana]

PTAL @ravindk89 @djwfyi @feorlen

[ravindk89]

Mostly clarifying questions on how parts of this would/should work.

[ravindk89]

Is this for arbitrary commands? Just an array list of strings to pass into a constructor, so I could do

- op: config
- command:
   - "mc"
   - "admin"
   - "config"
   - "set"
   - "config_setting"
   - "config_param=foo"
   - "config_param=bar"

Is this ballpark?

[jiuker]

Yesh

[ramondeklein]

I would still like to remove op in case command is used (it has no use in that case). Or use op: command and use the args as the command arguments. I think the current syntax is confusing.

[ravindk89]

Agree with ramon - it's sufficient to support name since that is what you would use dependsOn with. op is fully redundant.

[ravindk89]

As a note - how is this meaningfully different from the pre-baked paths?

I could also do

- op: mb
- command:
  - "mc"
  - "mb"
  - "--with-locks"
  - "myminio"
  - "foobar"

Right?

Also - assuming myminio is a preconfigured alias for the Tenant. Otherwise we have to specify what alias to use here.

[jiuker]

Yes. myminio is a preconfigured alias for the Tenant. Have a documentation at this markdown top line now.
Nothing different. @ravindk89

[jiuker]

op is optional now for this.
3fce527

[ramondeklein]

We may want to add a comment in YAML that this specifies user daniel with password: daniel123.

[ramondeklein]

I would still like to remove op in case command is used (it has no use in that case). Or use op: command and use the args as the command arguments. I think the current syntax is confusing.

[ravindk89]

OK from docs perspective this is a good baseline, and as Pedro noted the goal here is baseline, not complete.

As we iterate we can update this doc, which will eventually flow into the webdoc content.