Description of the operation hereThis operation deploys an Apigee API proxy or Shared flow to Apigee by using the maven apigee deploy plugin. You must have built artifacts as zip file or expanded folder, see Extract and Save Artifacts workflow on FlexDeploy - Apigee Plugin Guide page under Example Workflows. See Special Considerations below for details on folder structure. You can download zip file from Apigee and commit to SCM for use during build, or you can commit zip file in expanded format.
The plugin unzips any zipped file within the artifacts and will search for the API proxy or Shared flow folder and deploy it to Apigee. This operation automatically generated pom.xml and parent-pom.xml necessary to use with Maven for deployment.
Environment/Instance Properties
...
The artifacts folder must contain Apigee bundle that has a maven compatible file structure. To see what a maven compatible file structure looks like you can see the readme on the maven apigee deploy github page here.Below you can see the recommended folder structure for the project if it is an API proxy.
| Code Block | ||
|---|---|---|
| ||
|-gateway/ ***
|-test-app/
|-apiproxy/
|-proxies
|-resources/
|-py
|-policies
|-targets |
Below you can see the recommended folder structure for the project if it is a shared flow.
| Code Block | ||
|---|---|---|
| ||
|-gateway/ ***
|-test-app/
|-apiproxy/
|-proxies
|-resources/
|-py
|-policies
|-targets |