Document /etc/drlm/clients/[CLINAME].cfg.d directory

[peyoz]

Hi Guys,
I'm really enjoying drlm, thanks for the hard job!

I'm trying to understand what usage is the directory /etc/drlm/clients/{backup client}.cfg.d
I thought it could contain files with rear options to be sourced before the backup as addendum to /etc/drlm/clients/{backup client}.cfg, but I'm wrong.
I did some search and found something in the api code, but I don't understand completely the usage, can you please elaborate a little bit?
I'm trying to understand if I can drop there custom config for a client without having to modify the related cfg file

Thanks!

[didacog]

Hi @bloodmoon85,

We're pleased to know about people using and enjoying DRLM! You're welcome!

The /etc/drlm/clients/.cfg.d/ dir is the directory to store multiple backup configurations for the same client. Is not implemented, is prepared in the API, etc. but still need some changes in the DRLM workflows to work.

Eventually, we decided to implement this features in DRLM version 3, so this is the reason why is not finished in DRLMv2.x.

On the other hand, we have a customer who asked us to implement this and other features out of version 2 roadmap, sponsoring the development effort. We sent them the proposal and we are waiting for feedback.

So is a matter of time to have this feature, on DRLMv2.x (sponsorship) or in the new/future DRLMv3.

Hopefully your doubts are clarified..

Kind regards,
Didac

[didacog]

On the other hand, as you seem to have good skills, other option is that you implement it, and send a PR. We'll be pleased to help you to do it ;)

[peyoz]

Hi @didacog,
that would be a great idea.
How we shall proceed?

Edit: I found what I was looking for, how the curl line was created to download the configuration file, which is actually in rear source code.
I think a simple improvement in the drlm-api should go.
I'm not proficient in go, but I think I can get up to speed for the task.
:)

[didacog]

Hi @bloodmoon85,

First take a look at:
https://github.com/brainupdaters/drlm/blob/develop/CONTRIBUTING.rst
Then you can take a look inside drlm code, libs, locations, workflows, etc. to figure out a little bit how it works.
Before start, we must check what was the work we did in version 2 to allow multiple backups and what is missing to have a base to work on.
Then, we can open an issue in drlm repo to discuss the required changes and explain how you should proceed.

Sounds good to you? We are a little bit busy next weeks, so do not expect a fast recheck of what was done on this feature, but we'll talk soon after that.

If its ok, we gonna open the issue in drlm repo after we check the state of this half implemented feature and mention you in the issue to start discussing on it.

Kind regards,
Didac

[peyoz]

Ok,
I will wait on your input on how to proceed, I will have a look at the code meanwhile :)
Cheers!