Skip to content

Add validity check to deploy access levels

What does this MR do and why?

Add a check constraint to protected_environment_deploy_access_levels to ensure new entries have either user, group or access_level set

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

  1. Run the migration
  2. Validate the new check constraint exists by running \d protected_environment_deploy_access_levels; and see the check_deploy_access_levels_user_group_access_level_any_not_null exists

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #330483 (closed)

Merge request reports