Add a gate requirement to a delivery target

Open Gate requirements for the environment's repository target. With repository write access, enter the condition and check its preview before confirming it.

Add a requirement#

  1. Select Add requirement.
  2. Choose the Requirement and complete its fields. Its preview appears under On recorded decisions, or one line says why no decision can be replayed.
  3. Select Add requirement.
RequirementFields
Required keyKey name, and Provided as: Environment variable or Secret Manager secret on Cloud Run; Plain environment variable, Secrets Manager secret or SSM parameter on ECS. A key name uses letters, digits, _, . and -, and does not start with a digit.
Cloud Run ingressIngress: All traffic, Internal only or Internal and Cloud Load Balancing.
Cloud Run VPC egressVPC egress: All traffic or Private ranges only.
Cloud SQL connectionConnection name as project:region:instance, and Pool size in connections.
ECS reach to RDSRDS instance identifier and Port.
ECS capacityRunning tasks, and optionally CPU units and Memory in MiB.

Quantities are whole numbers from 1. An entry you add applies to every service the target binds. It is confirmed at once, and Added by names you. Adding a requirement that the target holds as a proposal for every service confirms that proposal; adding one it already holds confirmed changes nothing. A proposal for one service is a separate entry, which you confirm or dismiss on its own.

Search help

Tab to a result. Enter to open. Escape to close.