Add dast_profiles_tags table
What does this MR do and why?
We realized that runner tags should be linked to the Dast::Profile
instead of the DastScannerProfile
.
This Merge Request removes the table dast_scanner_profiles_tags
and adds the table dast_profiles_tags
.
The dast_scanner_profiles_tags
is not in use yet and as suggested in our guideline if the removing the old table and creating a new one is the preferred way to "rename" a table in that case.
Migrations
Remove dast_scanner_profiles_tags
up
main: == 20230106183904 RemoveDastScannerProfilesRunnerTags: migrating ==============
main: -- table_exists?(:dast_scanner_profiles_tags)
main: -> 0.0009s
main: -- drop_table(:dast_scanner_profiles_tags)
main: -> 0.0048s
main: == 20230106183904 RemoveDastScannerProfilesRunnerTags: migrated (0.0062s) =====
Add dast_profiles_tags
up
main: == 20230106184809 CreateDastProfilesTags: migrating ===========================
main: -- create_table(:dast_profiles_tags)
main: -> 0.0099s
main: == 20230106184809 CreateDastProfilesTags: migrated (0.0103s) ==================
down
main: == 20230106184809 CreateDastProfilesTags: reverting ===========================
main: -- drop_table(:dast_profiles_tags)
main: -> 0.0029s
main: == 20230106184809 CreateDastProfilesTags: reverted (0.0051s) ==================
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.