Deployment Scoped Variables
One of the deployment patterns we have been using from K8S is to generate unique configmaps per deployment of a service so that we can version variables with the code (but outside of the image). We have been able to achieve that using the existing Stack spec (nice work on this, btw), but it would be great if we could clean them up when the deployments get removed in the pipeline step.
Hey Michael, thanks for posting this and apologies for the delay in response. We've had quite a few people bring this up so the team is looking to frontload this into a coming release (possibly this week!).
Will make sure to keep you updated on that.
Join the conversation
Sign in with your Cycle account to reply to this thread.