Feature Request: Dynamic generated env config

[mageddo]

Summary & Motivation

Dynamic generated envs based on the JSON config file this way there won´t be necessary to create a manual env for every new config exposed at the config file.

Example:

Provide a solver which can solve from previously configured DNS records.
It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like.

Goals

What is supposed to do in short. (Optional)

Example

A simple, static DNS server

Non-Goals

What people would think it is supposed to do, but it is not? (Optional)

Example

• Not to implement a full and complex DNS server

Description

Explain the feature details and how it would work, usecases, examples, snippets of code,
inputs and outputs, etc. (Required)

Example

Storage

DNS records will be stored at the existing DPS config file.

DNS Records

• It will have support to A, AAAA and CNAME entries.
• Also, TTL by record will be supported