Is your feature request related to a problem? Please describe.
App developers need to "pin" to a specific version of a buildpack to be able to select a time-window in which to perform an update to a newer buildpack version.
For example in VM/BOSH world app developers can use the -b option specifying URL with tag/SHA:
--buildpack, -b Custom buildpack by name (e.g. my-buildpack) or Git URL (e.g. 'https://github.com/cloudfoundry/java-buildpack.git') or Git URL with a branch or tag (e.g. 'https://github.com/cloudfoundry/java-buildpack.git#v3.3.0' for 'v3.3.0' tag). To use built-in buildpacks only, specify 'default' or 'null'
Describe the solution you'd like
To be 100% backward compatible and have feature parity with VM/BOSH world the following should be possible:
upload the paketo stack in cache (blobstore/regirstry)
use the newly build stack for producing OCI image for the app
Describe alternatives you've considered
One might be able to:
build a custom buildpack stack using kpack/paketo CLI
upload the buildpack using cf create-buildpack
use the custom buildpack with -b <buildpack name>
This however requires
additional steps to be performed in app developer's CI/CD systems before every cf push
admin access to CF
Additional context
Connected to issue #340. This feature request is around the Git URL format supported by -b and the flow that allows app developers to use specific SHA of a buildpack, effectively delegating them the operational aspects around the buildpacks (security patching, deprecated use of languages and libraries, etc.)
Is your feature request related to a problem? Please describe. App developers need to "pin" to a specific version of a buildpack to be able to select a time-window in which to perform an update to a newer buildpack version.
For example in VM/BOSH world app developers can use the -b option specifying URL with tag/SHA:
Describe the solution you'd like To be 100% backward compatible and have feature parity with VM/BOSH world the following should be possible:
This might result the folowing on-the-fly flow:
Describe alternatives you've considered One might be able to:
cf create-buildpack
-b <buildpack name>
This however requires
cf push
Additional context Connected to issue #340. This feature request is around the Git URL format supported by
-b
and the flow that allows app developers to use specific SHA of a buildpack, effectively delegating them the operational aspects around the buildpacks (security patching, deprecated use of languages and libraries, etc.)