-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethinking the storage of API #29
Comments
I like "Project" and "Environment"
We might be able to pull this off without forking the API because we actually already put some effort in decoupling the storage from the rest of the architecture. |
As discussed after a call with @ryyppy, we decided to do the following:
|
I think we could rethink how the API stores it's data. Currently we are required to store data in the Hiera YAML format as our v3 infrastructure also uses this api in order to provision servers, etc.
The idea initially was that the v4 infrastructure uses the same exact same api and then in the future when everything is migrated we can remove the hiera YAML format and move to another storage system - I would call this process the parallel migration process.
I think though we should rethink this idea and have the following suggestion:
The text was updated successfully, but these errors were encountered: