This sample demonstrates how to use the Apigee Maven deploy plugin to deploy a sharedflow to Apigee using Cloud Build
- Provision Apigee X
- Access to deploy sharedflow to Apigee, trigger Cloud Build
- Configure external access for API traffic to your Apigee X instance
- Make sure the following tools are available in your terminal's $PATH (Cloud Shell has these pre-configured)
- gcloud SDK
- unzip
- curl
- jq
- npm
Use the following GCP CloudShell tutorial, and follow the instructions.
- Clone the apigee-samples repo, and switch the deploy-apigee-sharedflow directory
git clone https://github.com/GoogleCloudPlatform/apigee-samples.git
cd apigee-samples/deploy-apigee-sharedflow- Edit the
env.shand configure the ENV vars
PROJECTthe project where your Apigee organization is locatedAPIGEE_ENVthe Apigee environment where the demo resources should be created
Now source the env.sh file
source ./env.sh- Enable the Cloud Build API and assign Apigee Org admin role to the Cloud Build service account
gcloud services enable cloudbuild.googleapis.com
gcloud projects add-iam-policy-binding "$PROJECT" \
--member="serviceAccount:$CLOUD_BUILD_SA" \
--role="roles/apigee.admin"- Trigger the build
gcloud builds submit --config cloudbuild.yaml . \
--substitutions="_APIGEE_TEST_ENV=$APIGEE_ENV"Login to the Apigee console, click "Develop" and then "Shared Flows", you should see a sharedflow called sample-hello-ci-cd-sf imported and deployed.
If you want to clean up the artifacts from this example in your Apigee Organization, first source your env.sh script, and then run
./clean-up-deploy-apigee-sharedflow.sh