apiDeploy
- Karl Henselin
This operation creates an api deployment for each specification file to an API Gateway for the OCI tenancy. The apiDeploy operation can only be used with a FlexDeploy package-based deployment project of type Oracle API Gateway. On deploy execution, file level attributes COMPARTMENT_NAME, GATEWAY_NAME, and PATH_PREFIX determine if the api deployment should be created new or update an existing deployment the content of the specification file. That means path prefix must be unique for the given compartment-gateway combination for a new api deployment to be created.
Artifact is a single zip file containing api specification files (JSON or YAML).
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle API Gateway Account |
| No | OCI account with all the required properties like Tenancy Id, User OCID, and Private Key, etc. Oracle API Gateway Account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence. See Special Considerations below for instructions on how to create an OCI account for Oracle API Gateway. |
Compartment Name |
| No | The OCI compartment to deploy an api to. Useful if you deploy to a different compartment per environment. Compartment Name is required if Compartment Name on a file level attribute contains property replacement syntax - Property Replacement Support |
Gateway Name |
| No | The OCI gateway to deploy an api to. Useful if you deploy to a different gateway per environment. Gateway Name is required if Gateway Name on a file level attribute contains property replacement syntax - Property Replacement Support |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Root Compartment Id |
| Yes | Root or parent compartment Id used to find the sub-compartments for api deployment. i.e. ocid1.tenancy.oc1..<OCID> This can be sub-compartment as well, but root is suggested. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Oracle API Gateway Account |
| No | OCI account with all the required properties like Tenancy Id, User OCID, and Private Key, etc. |
Oracle API Gateway Replace List |
| No | The String and Value to replace in files, formatted as key=value. One pair per line. Lines that begin with '#' will be ignored. This is useful if you wish to do property replacement on your artifact and don’t want to change the source code to contain property replacement syntax from the beginning. // The key on the left will be replaced with the value on the right
dev-oic-vbcs-poc-idzor6zhmigm-ia.integration.ocp.oraclecloud.com:443=${{OIC_SERVICE_URL}}
${OrderService.url}=${{SOA_BASE_URL}}/soa-infra/services/defaults/OrderService/OrderService?WSDL |
Add Tags |
| No | Add defined tags when an API is created or updated and when an APIDeployment is created or updated. This is used to linked SCM commits and FlexDeploy deploy events to API and APIDeployment creation or updates. Default is true. The following defined tags will be added on build:
If Add Tags is enabled, and these tags do not exist, FlexDeploy will automatically create the tag namespace (FlexDeploy) and the tags within it. |
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
N/A
- style