Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DO NOT MERGE][CLOUD-2453][KEYCLOAK-7098] Deploy RH-SSO pod only if DB service is ready #60

Closed
wants to merge 2 commits into from
Closed

[DO NOT MERGE][CLOUD-2453][KEYCLOAK-7098] Deploy RH-SSO pod only if DB service is ready #60

wants to merge 2 commits into from

Commits on Oct 10, 2018

  1. [CLOUD-2453][KEYCLOAK-7098] Move description of SSO_ADMIN_USERNAME, 

    SSO_ADMIN_PASSWORD, SSO_SERVICE_USERNAME, and SSO_SERVICE_PASSWORD
variables from image.yaml to os-sso/module.yaml

These variables aren't used / referenced outside of some of os-sso,
os-sso71, and os-sso72 modules, and for the future we want one
common 'os-sso' module, sharing all the parts common to all
RH-SSO images. This move is part of such unification

Signed-off-by: Jan Lieskovsky <jlieskov@redhat.com>
    Jan Lieskovsky committed Oct 10, 2018
    Configuration menu
    Copy the full SHA
    b99e76e View commit details
    Browse the repository at this point in the history

  2. [CLOUD-2453][KEYCLOAK-7098] Deploy RH-SSO pod only if DB 

    service is ready, when provisioning from DB RH-SSO templates

Signed-off-by: Jan Lieskovsky <jlieskov@redhat.com>
    Jan Lieskovsky committed Oct 10, 2018
    Configuration menu
    Copy the full SHA
    b009d91 View commit details
    Browse the repository at this point in the history