Loading
Update DB docs to match how we re-generate them
What does this MR do and why?
This is to avoid any changes after db dosc are re-generated.
How to set up and validate locally
- On current
masterafter you rundb:migrate, there will be changes todb/docs/scan_result_policies.yml - On this branch there should be no changes to any file under
db/docsafterdb:migrate
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.