https://serverless-stack.com/ logo
Join Slack
Powered by
General question… In SEED UI we do bunch of config...
# seed
a
General question… In SEED UI we do bunch of configurations like “select a service”, or “select machine size”, all done from UI. Is there any intention to move this into code / config files? Similar to what we have for the steps execution (before build, after build, etc)… but for service / app configuration.
j
Not currently, but that’s something on the roadmap. Do you find yourself changing those settings?
a
I been changing the computing size.
I’m also using bitbucket pipelines, for example, and you can configure those params from there.
Also might be easier if I can index my services from code, not from UI.
Makes sense?
For example, we are going to add new services every month, we are growing the architecture fast enough. So I would need to go to the UI and configure each service every time.
j
Yeah adding services needs to be done through the UI. We might add a feature to auto-discover them at some point.
a
Yeah, that might be interesting. Or from config files also 🙂.
I’m using mono-repo, for example, so I can have some config file on the root, that you can read and pre-load the services from that definition.
And same applies for other parameters like computer size, etc.
j
Yeah adding service is interesting, because we don’t want to auto-remove them if somebody mistakingly changes the config. But the other service settings aren’t as sensitive.
a
Well, that’s true, maybe in that case we need some sort of API or SDK.
But well, maybe you can delete it from the config… and then you can recover it somehow from UI.
This is exciting, loving the product so far 😍 .
j
Awesome!
Thank you!
a
Thank you!!
Open in Slack
PreviousNext
Powered by