-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Deployment Stage DAG Enforcement #321
Comments
Hi! Looks like an interesting use case indeed. I think we can implement this in GTO. Do you use GTO already and need this to support your workflow? Or just considering whether to try it out? Also, want to clarify one thing: after running
you're expecting |
Hi @aguschin! This isn't part of a workflow yet. I'm just exploring data/model registry solutions, and, in learning how GTO works, I found that I'd want some type of deployment stage protection.
Correct, I'd expect |
Sounds good! Let me know if you'll need this - I can implement it shortly if you decide to use GTO. Adding to the backlog for now. |
I'm interested in enforcing that model versions are assigned to "lower" deployment environments (closer to dev) before they are allowed to be assigned to "higher" environments (closer to prod). I've drafted out an example below, and was curious if this feature would align w/ the goals for GTO?
For instance, to enforce the promotion DAG above, maybe an extension of the existing
STAGES
field in the.gto
file:Then during normal use you'd see:
The text was updated successfully, but these errors were encountered: