-
Notifications
You must be signed in to change notification settings - Fork 145
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
Fix kong permission and execution errors in wrapper.sh #45
Open
pieveee
wants to merge
9
commits into
supabase-community:main
Choose a base branch
from
pieveee:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the database provided is being disabled in values.yaml (e.g. because of using a replicated database solution) the helm installation would fail with: Error: INSTALLATION FAILED: template: supabase/templates/db/storage.yaml:1:14: executing "supabase/templates/db/storage.yaml" at <.Values.db.persistence.enabled>: nil pointer evaluating interface {}.enabled
Fix missing if-clause when database is disabled
Currently, the container for kong would not start as wrapper.sh fails in its execution with "Illegal option -o pipefail" (See: https://www.baeldung.com/linux/illegal-option-o-pipefail#how-to-avoid-the-error).
The /home/kong/ directory doesn't exist in the newest Docker image of kong. Hence, the kong.yml should be stored at an existing and writeable directory.
Fix kong permission issues
Change wrapper.sh execution from sh to bash
@milanvanschaik Can you check the merge request? |
@milanvanschaik @bigbitbus @icrotz @cpdeethree @devudopw @kiwicopple could you have a look? |
I don't have the rights to merge on this repository |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Currently, kong fails to start running with the following error:
And:
What is the new behavior?
/bin/sh
to/bin/bash
(See https://www.baeldung.com/linux/illegal-option-o-pipefail)/home/kong/kong.yml
to/usr/local/kong/kong.yml
, as well as/home/kong/template.yml
to/usr/local/template.yml
in order to runwrapper.sh
script without permission issues