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.
Previously the buildpack's S3 bucket was defined in two places - once in
VENDOR_URL
and again during the pip installation step. This duplication was necessary sinceVENDOR_URL
also contained the stack's name, whereas the pip use-case used a non-stack-specific S3 key prefix.In order to:
...the
VENDOR_URL
variable has been replaced withS3_BASE_URL
which no longer contains the stack name.The user-configurable override has similarly been renamed from
BUILDPACK_VENDOR_URL
toBUILDPACK_S3_BASE_URL
. Note: As before, this override cannot be set via standard app variables (see #989).The unused
USE_STAGING_BINARIES
environment variable has been removed, since it's a leftover from the project to stand up a staging S3 bucket. It's redundant given theBUILDPACK_S3_BASE_URL
variable.Closes W-8142401.