A mockup of what an automated API Lifecycle could look like
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1.9 KiB

Usecase "Hybrid - Open": Deploy an API on 3scale SaaS on self-managed APIcast and 3scale on-premises

In this usecase, a Jenkins pipeline will deploy an API described by an OpenAPI Specification file on a 3scale SaaS instance with self-managed APIcast and on a 3scale on-prem instance. The API is not secured as requested in the OAS.

Pre-requisites

Make sure you completed the SETUP guide.

Installation

Use the provided OpenShift template to install the Jenkins pipeline configured to target 3scale SaaS:

oc process -f hybrid-usecase-open/setup.yaml \
           -p DEVELOPER_ACCOUNT_ID="$SAAS_DEVELOPER_ACCOUNT_ID" \
           -p PRIVATE_BASE_URL="http://$BEER_CATALOG_HOSTNAME" \
           -p TARGET_INSTANCE=3scale-saas \
           -p PUBLIC_STAGING_WILDCARD_DOMAIN="$APICAST_SELF_MANAGED_STAGING_WILDCARD_DOMAIN" \
           -p PUBLIC_PRODUCTION_WILDCARD_DOMAIN="$APICAST_SELF_MANAGED_PRODUCTION_WILDCARD_DOMAIN" \
           -p NAMESPACE="$TOOLBOX_NAMESPACE" |oc create -f -

Use the provided OpenShift template to install the Jenkins pipeline configured to target 3scale on-prem:

oc process -f hybrid-usecase-open/setup.yaml \
           -p DEVELOPER_ACCOUNT_ID="$ONPREM_DEVELOPER_ACCOUNT_ID" \
           -p PRIVATE_BASE_URL="http://$BEER_CATALOG_HOSTNAME" \
           -p TARGET_INSTANCE=3scale-onprem \
           -p PUBLIC_STAGING_WILDCARD_DOMAIN="$APICAST_ONPREM_STAGING_WILDCARD_DOMAIN" \
           -p PUBLIC_PRODUCTION_WILDCARD_DOMAIN="$APICAST_ONPREM_PRODUCTION_WILDCARD_DOMAIN" \
           -p DISABLE_TLS_VALIDATION=yes \
           -p NAMESPACE="$TOOLBOX_NAMESPACE" |oc create -f -

Deployment

Deploy the API to 3scale SaaS:

oc start-build hybrid-usecase-open-3scale-saas

Deploy the API to 3scale on-prem:

oc start-build hybrid-usecase-open-3scale-onprem