Service Provider Integration Deployment

Post-bootstrap Service Provider Integration(SPI) Configuration

SPI requires Service Provider to have configured OAuth application so it can process the OAuth flow. Follow Configuring Service Providers in SPI admin documentation.

Authorization URL of staging server: https://spi-oauth-spi-system.apps.appstudio-stage.x99m.p1.openshiftapps.com
Callback URL of staging server: https://spi-oauth-spi-system.apps.appstudio-stage.x99m.p1.openshiftapps.com/oauth/callback

NOTE: Following process is automated in preview mode

SPI components will fail to start right after the bootstrap as additional manual configuration is required before they are healthy.

1. Edit ./components/spi/base/config.yaml see SPI Configuration Documentation.

2. Create a shared-configuration-file Secret

kubectl create secret generic shared-configuration-file --from-file=components/spi/base/config.yaml -n spi-system

1. In few moments, SPI pods should start

SPI Vault instance has to be manually initialized. There is a script to help with that:

1. Make sure that your cluster user has at least permissions.

2. Clone SPI operator repo

git clone https://github.com/redhat-appstudio/service-provider-integration-operator && cd service-provider-integration-operator

1. run vault-init.sh script from repo root directory

`./hack/vault-init.sh`