Feature Request: default location for config file and pre/post scripts

[ZetaMap]

It's possible or not to have a feature that search in a default location to get the config and pre/post scripts?
Like that, we can just edit the config in /etc/mysql-backup/config.yml, for example, and run mysql-backup dump without arguments.

For me, this would be a great feature, as I'm currently creating an Exherbo package of your tool, which I'll then use in an Ansible role to automatically generate and deploy configurations to database VMs.
This way, with another Ansible role, I could run a backup of all the VMs by simply running "mysql-backup dump --target=s3" and upload them to the S3 target.

[deitch]

I don't see why not? Set it here. Just make sure that it doesn't trigger this.

That second section is meant to ensure that if we cannot find the config file then:

• if the user never set a config file, it is fine, keep going.
• if the user explicitly set a config file, then the file must be found or error out.

I did something like that elsewhere, recently, the correct magical incantation was:

			if cmd.Flags().Changed("config-file") {

to determine if it was changed. Perfectly fine not to find the file if the user never changed it.

[ZetaMap]

ok. Also, I noticed that the documentation on the config file format is not very clear. One paragraph says to configure something like this, then another in another file says that it must be done in another way, and the example files show other methods. So I'm a little confused about how to format the file.

Like for scheduling:

configuration.md said like that:

dump:
  schedule:
    frequency: 60

but scheduling.md said:

dump:
    frequency: 60

or for targets, e.g. s3; the local.yaml example said:

    s3:
      type: s3
      url: s3://bucket.us-west.amazonaws.com/databackup
      details:
        region: us-west-1
        endpoint: https://s3.us-west-1.amazonaws.com
        accessKeyId: access_key_id
        secretAccessKey: secret_access_key

but configuration.md said to put "spec" instead of "details,
and the telemetry.yaml example said:

    s3:
      type: s3
      url: s3://bucket.us-west.amazonaws.com/databackup
      region: us-west-1
      endpoint: https://s3.us-west-1.amazonaws.com
      credentials:
        accessKeyId: access_key_id
        secretAccessKey: secret_access_key

...
And so on, for many things.

Idk if the docis old, but it should be updated, because I'm a bit confused.

[deitch]

Yes, some of the config examples were more emergent than planned. It is a good idea to go over them and make sure they all match the spec.

Will you open a PR on the default config location?

[deitch]

#444 fixed the examples

[ZetaMap]

Will you open a PR on the default config location?

Honestly, i don't really have the time for, it was during my internship period, and right now I'm focused on making my report. Also i never programmed in Go, so I don't really know how to go about it.

Probably i will do that, if i have time, later... Sorry