-
Notifications
You must be signed in to change notification settings - Fork 22
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
Use bots to trigger kebechet updates and make releases. #2584
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
4 tasks
/triage accepted |
1 task
/kind feature |
By alembic changes, do you mean SQL schema changes which would require a migration ? In that case, we might want to use a postsubmits job on thoth-storages and then cascade the changes ? |
As we dont want to do it via a github bot, we are updating the acceptance criteria Possible options
or
Acceptance criteria
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As we use bots to monitor the system, it would be helpful if we could monitor storage with alembic changes and make a release in the required component for the release, so we can keep all the components fresh with the database schema.
The text was updated successfully, but these errors were encountered: