fix: fall back to default command when Procfile key is missing - #8
Open
yahyanaujid wants to merge 1 commit into
Open
yahyanaujid wants to merge 1 commit into
yahyanaujid wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes the silent-empty-script bug from kubero-dev/kubero#795.
When a Procfile exists but is missing a build:, web:, or worker: key, the corresponding init-.sh script was written empty instead of falling back to KUBERO_BUILDPACK_DEFAULT__CMD — the fallback only ran when there was no Procfile at all. This moves the fallback check outside the Procfile branch so it applies whenever the extracted command is empty, for all three script types (the issue only reported build:, but web:/worker: have the identical bug).