Cleanup bs_request_action attributes after validations got introduced#19220
Open
krauselukas wants to merge 1 commit intoopenSUSE:masterfrom
Conversation
We cleaned up and corrected some validations performed on the `bs_request_action` models in openSUSE#19178. After those validations proven to be correct, we can cleanup the database with a data migration. Co-authored-by: Jay Michalska <jay.michalska@suse.com>
krauselukas
added
Frontend
eduardoj
requested changes
Feb 2, 2026
Member
eduardoj
left a comment
eduardoj
left a comment
There was a problem hiding this comment.
Update on version in src/api/db/data_schema.rb is missing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We cleaned up and corrected some validations performed on the
bs_request_actionmodels in#19178. After those validations proven to be correct, we can cleanup the database with a data migration.
The data migration got extracted from previously mentioned PR in order to be performed independently after the validations proved to be correct once used in production.
DO NOT MERGE: Lets double check if the validations turned out to behave correctly on all of our production systems.