A Seed feature request.
Some (most) of our apps ha...
# seedr
Ross Coundon
07/19/2021, 8:06 PMA Seed feature request.
Some (most) of our apps have a lot of env vars. Since env vars are only updated upon a redeploy, it's quite easy to change an env var but forget to redeploy and then confusion reigns as the expected behaviour doesn't match the actual. Or, the env var gets applied later when the app is auto-deployed.
So, what would be great was if there was some kind of visual indicator on the pipeline view to highlight that there are not-deployed env vars, and on the env var screen, a highlight of the specific vars that aren't deployed
f
Frank
07/19/2021, 9:10 PM
Yup, that makes sense. Added to the roadmap.
Frank
07/19/2021, 9:11 PM
Based on what you described, I think it also makes sense to forces the subsequent deployment after making an env var change, so services don’t get skipped b/c no code changes detected.
r
Ross Coundon
07/19/2021, 9:44 PMYeah that makes sense, although I've never actually seen a build get prevented due to no code changes
Ross Coundon
07/19/2021, 9:45 PMDid you guys get any further with the env var upload item or making the Seed roadmap of changes public?
f
Frank
07/19/2021, 10:29 PM
Oh yeah, just saw that you have 1 SLS service per repo. Nvr mind that.
Frank
07/19/2021, 10:31 PM
Not yet, but we are expanding the team atm and are going to get through the backlog in the next few weeks!
r
Ross Coundon
07/20/2021, 6:24 AMGreat news Frank!