Closed mika666 closed 6 years ago
maybe reuse core.cmd and just add a ref to it to api and expose it via env cfg controller?
this way one would just have to deploy the api apps and make sure a db is present, and then run all the maintenance remotely without ever having to remotely expose a database
looks like doesn't make sense any longer
- [ ] access token for remote env cfgfor the time being it is handled via user that is granded access to the masterofpuppets application; since this app is meant to provide full env management functionality, it is ok to keep it this way. full cmd functionality possible to execute remotely:- [ ] db creationthis is a bit pointless, as in order to authenticate against an envcfg API need to call identity server and it requires identity db & operationaldb to be set up already- [x] morgalready possible, so can create master orgs remotely- [ ] upgrade dbsapis can migrate their db defs upon start, so this is no longer a vlaid requirement etc?- [ ] move cmd core cfg bits and pieces into mh core env cfg perhaps? so API can share it with CMD.cmd core handler is a library already, so pretty much reusable (although perhaps console calls may explode in asp net core