The purpose was exactly this one, to make visible as configuration option something that was not only in the functional code, but useful in various situation. Of course, it is bash and any variable can be set via environment, but it seemed not right to dig in the code to find internal stuff and see how one can overwrite it -- better make it explicit in the config file (and I also aligned it to the naming pattern for the rest of db vars).

It would be good from people/community to propose changes/enhancements when they need something and it is not a configuration option, otherwise a developer may not have an idea who is using some hidden internal stuff.
Not really like that given is shell, but this would sound like: in a C code blaming that a dev did a rename of a variable because someone does a sed to replace the old one before compilation with something else.

Then I do not even remember when kamdbctl version was bumped, but was nothing like done periodically or on changes, but I agree could have been something good to do.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.