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.

Sign up for GitHub

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

Jump to bottom

[spike][2pt] Research on methods to trigger automatic schema update. #2582

Open
Tracked by #2145
harshad16 opened this issue Jun 2, 2022 · 3 comments
Open
Tracked by #2145

[spike][2pt] Research on methods to trigger automatic schema update. #2582

harshad16 opened this issue Jun 2, 2022 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

harshad16 commented Jun 2, 2022 •
edited
Loading

Research a mechanism that runs schema updates on each release.
schema updates can be done via management-api API call using https://management.prod.thoth-station.ninja/api/v1/ui/#/Graph/initialize_schema
we would like to trigger this schema update on each release, instead of doing it manually.
@harshad16 harshad16 mentioned this issue Jun 2, 2022
Open
4 tasks
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Jun 2, 2022
@harshad16 harshad16 changed the title Research on methods to trigger automatic schema update. [spike][2pt] Research on methods to trigger automatic schema update. Jun 2, 2022
@harshad16
Copy link
Member Author

/triage accepted
/priority important-soon

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jun 3, 2022
@harshad16 harshad16 mentioned this issue Jun 3, 2022
Closed
@harshad16 harshad16 added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label Jun 6, 2022
@goern
Copy link
Member

goern commented Aug 9, 2022

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 9, 2022
@harshad16 harshad16 moved this to New in SIG-DevSecOps Sep 22, 2022
@VannTen
Copy link
Member

VannTen commented Sep 22, 2022

I think we should look into ArgoCD hooks. The first example on that page is precisely a DB migration.

@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 🆕 New
SIG-DevSecOps
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @VannTen @harshad16 @sesheta