Is your feature request related to a problem? Please describe.
The current system is kind of a mess and does not allow for much processing in the form of how to format data and where to put it.
Yes the "final form" is a dotenv file, but what if the system (like az func) expects a settings.local.json file? or we want to quickly share secrets through onetimesecret.com, or even grab data from a given url from onetimesecret?
Describe the solution you'd like
clear separation of data pipeline processes:
- Source: some external source that inputs data to out system (ie "Import")
- Format: how to convert array of stored env values to a given format
- Writer: how to "export" that data
commands that follows normal data flow (all under !env context):
.. import --from 'thing' -as 'format' (there should probably some autodiscover here that can figure out the formatting)
.. export --to 'otherthing' -as 'format'
Is your feature request related to a problem? Please describe.
The current system is kind of a mess and does not allow for much processing in the form of how to format data and where to put it.
Yes the "final form" is a dotenv file, but what if the system (like az func) expects a settings.local.json file? or we want to quickly share secrets through onetimesecret.com, or even grab data from a given url from onetimesecret?
Describe the solution you'd like
clear separation of data pipeline processes:
commands that follows normal data flow (all under !env context):
.. import --from 'thing' -as 'format'(there should probably some autodiscover here that can figure out the formatting).. export --to 'otherthing' -as 'format'