Lines Matching full:prod
112 projects/foo/releases/prod | projects/foo/rulesets/uuid123
113 projects/foo/releases/prod/beta | projects/foo/rulesets/uuid123
114 projects/foo/releases/prod/v23 | projects/foo/rulesets/uuid456
116 The table reflects the `Ruleset` rollout in progress. The `prod` and
117 `prod/beta` releases refer to the same `Ruleset`. However, `prod/v23`
138 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
180 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
259 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
302 Example 1: A filter of 'name=prod*' might return `Release`s with names
303 within 'projects/foo' prefixed with 'prod':
307 projects/foo/releases/prod | projects/foo/rulesets/uuid1234
308 projects/foo/releases/prod/v1 | projects/foo/rulesets/uuid1234
309 projects/foo/releases/prod/v2 | projects/foo/rulesets/uuid8888
311 Example 2: A filter of `name=prod* ruleset_name=uuid1234` would return only
312 `Release` instances for 'projects/foo' with names prefixed with 'prod'
317 projects/foo/releases/prod | projects/foo/rulesets/1234
318 projects/foo/releases/prod/v1 | projects/foo/rulesets/1234
346 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
398 `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
433 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`
475 # `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`