nicolas
/
API-Lifecycle-Mockup
mirror of https://github.com/nmasse-itix/API-Lifecycle-Mockup.git
1
0
Fork 0
Code Issues Releases Wiki Activity
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.
46 Commits
1 Branch
0 Tags
81 KiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
API-Lifecycle-Mockup/multi-environment-usecase
Nicolas Massé 67cc5fc821
add doc and prepare for transfer 		7 years ago
..
Jenkinsfile add doc and prepare for transfer 7 years ago
README.md add doc and prepare for transfer 7 years ago
setup.yaml add doc and prepare for transfer 7 years ago
swagger.yaml add doc and prepare for transfer 7 years ago

README.md

Usecase "Multi-environment": Deploy an API in three environments, all in one tenant

In this usecase, a Jenkins pipeline will deploy an API described by an OpenAPI Specification file on a 3scale SaaS instance, in three environments: DEV, TEST and PROD. The API is secured using API Keys as described in the OAS.

Pre-requisites

Make sure you completed the SETUP guide.

Installation

Use the provided OpenShift template to install the Jenkins pipeline:

oc process -f multi-environment-usecase/setup.yaml \
           -p DEVELOPER_ACCOUNT_ID="$SAAS_DEVELOPER_ACCOUNT_ID" \
           -p PRIVATE_BASE_URL="http://$EVENT_API_HOSTNAME" \
           -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 -

Deployment

oc start-build multi-environment-usecase