Deploys an API to a Logical Gateway and any configured Nodes for that Gateway. The API deployed is determined by the FDOAP_API_NAME and FDOAP_API_VERSION properties and the optional FDOAP_INP_API_ITERATION input.
This operation can also be used to undeploy, activate or inactivate a deployment depending on the Deploy Action input.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle API Platform Account |
| Y | The Oracle API Platform cloud account to use for this operation. |
Oracle API Gateway Id |
| Y | The Logical Gateway Id to use for deployments. This is found in the header drawer (3 vertical dots) when inspecting the Logical Gateway in API Platform. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle API Name |
| Y | Name of the API being managed |
Oracle API Version |
| Y | Version of the API being managed |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Deploy Action |
| Y | Action to use when deploying. Valid choices are DEPLOY, UNDEPLOY, ACTIVATE, and INACTIVATE. |
API Runtime State |
| Y | The runtime state of the API after deployment. This only applies when the Deploy Action input is 'DEPLOY'. Valid choices are ACTIVE and INACTIVE. |
API Status |
| N | Optionally set the API status after deployment. Valid choices are ALPHA, BETA, DEPRECATED, RELEASED, and RETIRED |
Deployment Description |
| N | Description for the deployment request. This shows up in the API deployments section under the Logical Gateway name. |
API Iteration |
| N | Optional API Iteration to deploy. If this is left blank, then the current iteration on the API Platform server will be deployed. |
Deploy Wait Duration |
| N | Time to wait (in milliseconds) for the deploy request to complete. The deploy request is submitted immediately and then monitored for success for this duration. If time runs out before it succeeds the request will not fail but rather gracefully end with a warning. |
...
If your deploy workflow is not running the ImportAPI step, then I recommend you save the output API Iteration from ExportAPI to a file during the build workflow. You can then read that file in during deploy. Check out these build/deploy workflows:
If you deploy workflow does have the import step prior to deployment, then you can simply use the output returned from that step.
...
Finding the Gateway Id Target property
...
...