feat(plugins): Support bootstrap configuration

[sanderob]

This PR solves the need for Python configuration that is executed before plugins are imported. The configuration is appended to configuration.py, through the key extraBootstrapConfig. This PR is created in relevance to an existing issue.

Fixes #1043

[LeoColomb]

Thanks for submitting this pull request, @sanderob.
I'm advocating to avoid adding any new values as much as possible.
What about simply moving the config loading after the DATABASE config?

netbox-chart/charts/netbox/files/configuration.py

Line 58 in 5c8e68f

_load_yaml()

[sanderob]

Thanks for submitting this pull request, @sanderob. I'm advocating to avoid adding any new values as much as possible. What about simply moving the config loading after the DATABASE config?

netbox-chart/charts/netbox/files/configuration.py

Line 58 in 5c8e68f

_load_yaml()

Hi @LeoColomb!

I believe your suggestion to move the configuration loading (_load_yaml()) is due to a plan to include the relevant configuration through the extraConfig functionality of the chart? It seems this is for yaml-files only, as seen here:

extra_config_base = Path("/run/config/extra")
config_files = [Path("/run/config/netbox/netbox.yaml")]

config_files.extend(sorted(extra_config_base.glob("*/*.yaml")))

However, the necessary configuration is native python code, for example the following:

from netbox_branching.utilities import DynamicSchemaDict
DATABASES = DynamicSchemaDict(DATABASES)
DATABASE_ROUTERS = ['netbox_branching.database.BranchAwareRouter']

I am open to solve this without adding any additional keys. Are you aware of any methods for including (and executing) python code as any form of additional config?

[sanderob]

@LeoColomb I am adding a small reminder here :)