Environment layer

I think the suggestion to add a new data layer has a place.

Case: When initializing a project, you can specify certain parameters in CI/CD and then override them in the database.

Code (link):

# shortcut
@staticmethod
def _get_from_env(name):
    return environ.get(name, None)

# updated method
@classmethod
def get(cls, name, default=None):
    val = cls._get_from_cache(name)
    if val is None:
        val = cls._get_from_database(name)
        if val is None:
            val = cls._get_from_env(name)
            if val is None:
                val = cls._get_from_settings(name)
                if val is None:
                    val = default
    return val

[InzGIBA]

It would also be interesting to have a solution to switch the priorities of the data sources.

A possible solution is to create a map, in the form of a dictionary that matches keys and functions (values) and cycles to the first find.

Examples:

1. cache
2. database
3. env
4. settings

---

1. cache
2. database
3. settings
4. env

etc…

[fabiocaccamo]

@InzGIBA I’m not convinced about this approach, I would like to keep it very simple as it is now, I will think about this…