-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
make deploy script mac os friendly #6560
Conversation
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/3973/ |
@riuvshin why Mac Os friendly? And you are updating it here and not in master branch because you are supposed to merge it to master by the end of the week anyway right? |
sed "s| keycloak-oso-endpoint:.*| keycloak-oso-endpoint: ${KEYCLOAK_OSO_ENDPOINT}|" | \ | ||
sed "s| keycloak-github-endpoint:.*| keycloak-github-endpoint: ${KEYCLOAK_GITHUB_ENDPOINT}|" | \ | ||
sed "s/ keycloak-disabled:.*/ keycloak-disabled: \"${CHE_KEYCLOAK_DISABLED}\"/" | \ | ||
if [ "${CHE_LOG_LEVEL}" == "DEBUG" ]; then sed "s/ log-level: \"INFO\"/ log-level: \"DEBUG\"/" ; else cat -; fi | \ | ||
sed "$MULTI_USER_REPLACEMENT_STRING" | \ | ||
if [ "${ENABLE_SSL}" == "false" ]; then sed "s/ che-openshift-secure-routes: \"true\"/ che-openshift-secure-routes: \"false\"/" ; else cat -; fi | \ | ||
if [ "${ENABLE_SSL}" == "false" ]; then sed "s/ che-secure-external-urls: \"true\"/ che-secure-external-urls: \"false\"/" ; else cat -; fi | \ |
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.
You can combine these lines
# ---------------- | ||
# helper functions | ||
# ---------------- | ||
append_after_match() { |
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.
Can you describe what it is used for in line comments
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.
OK for me, unless it might have been 2 PRs: one PR to make it macOS friendy (only related to multiuser additions => on the che-multiuser
branch), and one PR to synchronize deploy scripts, that could have been made on master.
@l0rd there was used variation of |
agree with @davidfestal I will introduce separate PRs |
@davidfestal @l0rd here is sync PR to master #6566 once it will be merged I will update this PR |
@l0rd @davidfestal PR is updated :) |
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/3990/ |
What does this PR do?
synchronize deploy script from rh-che, make it mac os friendly