-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
Introduction of Red Hat Build of Keycloak #202
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sabre1041 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
5430e7c
to
dcfc3f3
Compare
Signed-off-by: Andrew Block <andy.block@gmail.com>
Signed-off-by: Andrew Block <andy.block@gmail.com>
@@ -100,15 +100,16 @@ jobs: | |||
# wait for a while to be sure CRDs are installed | |||
sleep 1 | |||
kubectl create -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.25.0/olm.yaml | |||
kubectl create --kustomize keycloak/operator/overlay/kind | |||
oc create namespace keycloak-system --dry-run=client -o yaml | oc apply -f- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious - what is the benefit of --dry-run
and then piping it through oc apply
?
Migration from RHSSO -> RHBK
tas-easy-install.sh
script updated and testedtas-env-variables.sh
script updated and tested