Feat. Add database naming strategy

[sleipnir]

Includes the possibility of not forcing the use of the namespace in the name composition.

[mruoss]

Thanks @sleipnir
Seems something is off with the workflows... I will check it...

[mruoss]

Hey @sleipnir

• The issues with the pipeline should be fixed on main, please rebase.
• I find the code a bit cumbersome. Why not go shorter like this and spare the conversion logic:

using_prefix_strategy? = resource["spec"]["usingPrefixNamingStrategy"] != "false"
db_name = Database.name(resource, prefix_namespace: using_prefix_strategy?)

Note I've changed the second argument of Database.name/2 to be a keyword list (opts). I don't like flags without the scope as function vars.

I can take it from here if you want.

[sleipnir]

Perfect for me. I prefer to use pattern matching than chained map calls but ok.
I agree with using Keyword, I had started this way but I decided to change it because it was something very simple and I didn't see other options that could justify a list.

[sleipnir]

Hi @mruoss I believe that now everything is ok. Can you review it again please?

[mruoss]

Thanks @sleipnir, I'll merge this.

I will add a changelog entry and I might change the field from boolean to string before releasing it (i.e. databaseNamingStrategy: none | prefix_namespace instead of usingPrefixNamingStrategy: true | false where prefix_namespace is the default).

BTW: I'm prefixing the namespace per default so there's no conflicts if we have db resources with the same name in different namespaces. But if the user overrides this manually, that's okay I guess.