If your ReleaseOps deployment request has custom states, you must configure the Deployment Request State Map table so that your ReleaseOps deployment request states map to the correct App Engine states.
Before you begin
Role required: admin or app_engine_admin
Procedure
-
On your production instance, navigate to .
-
Select the ReleaseOps deployment request state in the ReleaseOps DR state column that you want to update.
Important: It's not recommended to change the mapping of any
ReleaseOps deployment request end states, including:
- Canceled
- Completed
- Failed
-
On the state mapping record page, select the value in the App Engine DR state field that corresponds to the ReleaseOps deployment request state.
- Optional:
In the Notes field, enter additional details about the state mapping.
-
Select Update or select and hold (or right-click) in the header and select Save to update the record.
- Optional:
Repeat the procedure in steps 2 through 5 for each deployment request state that you want to update.
-
To create a deployment request state mapping record, select New on the Deployment Request State Maps table.
You can create a deployment request state mapping record when there are more or new ReleaseOps deployment request states that must be mapped onto corresponding App Engine deployment request states.
-
In the App Engine DR state field, select the App Engine deployment request state from the list.
-
In the ReleaseOps DR state field, select the corresponding ReleaseOps deployment request state.
- Optional:
In the Notes field, enter additional details about the state mapping.
-
Select Update or select and hold (or right-click) in the header and select Save to update the record.
Result
You have mapped all ReleaseOps deployment request states onto the corresponding App Engine deployment request states.
What to do next
If you want to configure additional conditions to enable migration to ReleaseOps, see Add custom conditions to enable ReleaseOps deployments.