Allow configuration of API server through config file

[CathalOConnorRH]

Prep work for TEP-0117 to allow future configuration options through config file.

This change allows for both config file options and env var options, where the env var will override the config file option if it is set.

[tekton-robot]

Hi @CathalOConnorRH. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[adambkaplan]

Do we want to allow DB credentials to be stored in plaintext? Will Viper also allow these to be set with env vars, and the other settings to be populated via the file?

[CathalOConnorRH]

it's optional to have the password in the config file, if a config item is set as a env var, viper will use that over the config file version [1] AutomaticEnv.

1. AutomaticEnv

[adambkaplan]

A question for the maintainers (@dibyom, perhaps) - is it worth updating the api.yaml manifest to mount a ConfigMap with a config file that contains non-sensitive info (example - db name, address, protocol?)

[dibyom]

A question for the maintainers (@dibyom, perhaps) - is it worth updating the api.yaml manifest to mount a ConfigMap with a config file that contains non-sensitive info (example - db name, address, protocol?)

Sounds good as long as we don't allow passwords over config maps

[dibyom]

/ok-to-test

[dibyom]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dibyom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[enarha]

/kind feature