Build image & Deployment process of creating image and installing Payment Building Block Adapter in EKS cluster.
Note that pipeline also includes Payment Building Block emulator deployment. Docs
Context
Description
sandbox-dev
Context containing all needed env-vars for image creation and deployment to sandbox-dev cluster
playground
Context containing all needed env-vars for image creation and deployment to playground cluster
Circle CI pipeline parameters:
Name
Type
Default
Effect
emulator_namespace
string
payment-bb-emulator
defines the namespace for the deployment in k8s cluster
adapter_namespace
string
payment-bb-adapter
defines the namespace for the deployment in k8s cluster
playground
boolean
false
defines that build and deploy should be executed to playground environment
emulator_image
string
"bb/payments/emulator"
base path of the image in the respective environment ECR
adapter_image
string
"bb/payments/adapter"
base path of the image in the respective environment ECR
force_deploy
boolean
false
used to force-deploy on dev cluster when branch is not main
emulator-db-flush
boolean
false
to install the emulator in development mode (on restart to reinit the database in initial state)
Use-case
Description
Branch
Param Values
Build image in dev environment
Builds image and uploads it to dev env
Not main
-
Build & Deploy image in dev environment
Builds image, uploads it to dev env and deploys the application to dev cluster
main
-
Build & Deploy image in dev environment
Builds image, uploads it to dev env and deploys the application to dev cluster
Not main
"force_deploy" set to "TRUE"
Build & Deploy image in playground environment
Builds image, uploads it to playground env and deploys the application to playground cluster
main
"playground" set to "TRUE"
"emulator-db-flush" pipeline parameter can be set to "TRUE" for any of the use-cases.
Circle CI Deploy Workflow:
To run follow those steps:
navigate to project in CircleCI
select branch from the dropdown
select "Trigger pipeline" action
Apply pipeline params if needed based on Circle CI use-cases
Then trigger the pipeline