Skip to content
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

Sequelize Cleanup #714

Open
FancMa01 opened this issue Mar 26, 2024 · 0 comments
Open

Sequelize Cleanup #714

FancMa01 opened this issue Mar 26, 2024 · 0 comments

Comments

@FancMa01
Copy link
Collaborator

FancMa01 commented Mar 26, 2024

Clean up Sequelize

  1. Only one migration for one model
  2. Any migration to alter the table must check if the alteration has already been completed
  3. A proper relationship is established, so action cascades from parent to child

Notes - Deleting Application must delete all associated resources
Deleting Cluster - should not cascade to JM or any other monitoring. Instead, a warning should be displayed explaining any monitoring, or workflows with this cluster ID will fail. This gives users the option to update clusters in existing monitoring and workflows

@ydahal1 ydahal1 changed the title Cluster removal does not cascade to job monitoring Sequelize Cleanup Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant