Hey just wanted to add this to one of my earlier suggestions about env vars and then overrides per stage. I like the pipeline setup currently where you have a stage where multiple deployments can be made on that stage but just ran into an issue where I waiting like 15 minutes for build + deploy only to realize it went on the wrong aws account so had to enter in my credentials and redo. Instead of creating all of the different stages for us I think it would be cool if we could create the different stages ourselves with our own names and when we create a new stage it would prompt to enter in the defaults for that stage as far as environment variables (and overrides from any app wide defaults), aws credentials, notifications etc. Would probably require a lot of changes on y'alls end but way better user experience imo.

Hey @Garret Harp

Instead of creating all of the different stages for us I think it would be cool if we could create the different stages ourselves with our own names

SEED only auto-creates stages for new branches and PRs if the branch and PR workflow are enabled. For non-ephemeral stages (ie. dev, staging, preprod, prod, etc) they have to be created by the user. Here’s the flow https://seed.run/docs/adding-a-stage

I guess I mean the pipeline, so like under development/staging/production there can be many stages. But there isnt a way to define the notification options, env cars, or iam role for the entire group of stages. You can copy settings from an existing stage when you make a new one but just having defaults on the pipeline it is associated with would be a bit nicer.

Ah gotcha. Lemme add that to the roadmap!