Documenting known issue: pack 0.33.0 has breaking change for library users #2071
Labels
documentation
status/ready
Issue ready to be worked on.
type/bug
Issue that reports an unexpected behaviour.
Description
This was reported in Slack: https://cloud-native.slack.com/archives/C033DV8D9FB/p1708014910021369
Previously,
build.LifecycleOptions.UID
didn't exist as a field / options for the "lifecycle executor".When we merged #2017 we didn't realize that in order for the "lifecycle executor" to work properly the
l.opts.UID
must be set intentionally, to either:-uid
to the lifecycleIf
l.opts.UID
is unset (0) then a number of issues can occur:Proposed solution
When upgrading to 0.33.0, pack library consumers MUST set
build.LifecycleOptions.UID
to either a positive or negative value. It cannot be 0.Describe alternatives you've considered
We could roll back #2017. But, a similar requirement has already existed for some time for
build.LifecycleOptions.GID
.The text was updated successfully, but these errors were encountered: