modify api to allow expressing if previous entrypoints should be overridden#103
Merged
modify api to allow expressing if previous entrypoints should be overridden#103
Conversation
bcmyers
force-pushed
the
bcmyers/entrypoint
branch
4 times, most recently
from
47d78bf to
1cf35c0
Compare
andrew-lockwood
approved these changes
Sep 23, 2025
bcmyers
force-pushed
the
bcmyers/entrypoint
branch
from
1cf35c0 to
a0e82da
Compare
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
2 participants
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.
On
oci_image, if a user does not provide anentrypoint, i.e. (entrypoint == None), that should mean do nothing with the entrypoint for this layer, potentially inheriting the entrypoint from previous layers. Without this change, settingentrypoint == Nonewould always overwrite the entrypoint from previous layers to be[], which may not be the behavior the user wants.