The following instructions explain how to get started when cf.tokenProvider
is set to userpass
Authenticate to a foundation using the API endpoint.
E.g., login to IBM Cloud
cf login -a api.us-south.cf.cloud.ibm.com -u <username> -p <password>
The following instructions explain how to get started when cf.tokenProvider
is set to sso
Authenticate to a foundation using the API endpoint
E.g., login to Dhaka
cf api https://api.sys.dhaka.cf-app.com
cf login --sso
Visit the link in the password prompt to retrieve a temporary passcode, then complete the login process
E.g.,
https://login.sys.dhaka.cf-app.com/passcode
)
Inspect the contents of ~/.cf/config.json
and copy the value of RefreshToken
.
Paste the value as the value for CF_REFRESH-TOKEN
in your config/secrets.json
{
"CF_TOKEN-PROVIDER": "sso",
"CF_API-HOST": "xxxxx",
"CF_REFRESH-TOKEN": "xxxxx",
}
Please review the manifest.yml before deploying.
Deploy the app (w/ a user-provided service instance vending secrets)
./scripts/deploy.sh
Deploy the app (w/ a Credhub service instance vending secrets)
./scripts/deploy.sh --with-credhub
Shutdown and destroy the app and service instances
./scripts/destroy.sh
Note: If you are seeing OutOfMemory exceptions shortly after startup you may need to cf scale the available memory for large foundations. You may also need to adjust
JAVA_OPTS
environment variable and increase the amount of direct memory available via-XX:MaxDirectMemorySize
.