Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhanced run image resolution #357

Conversation

c0d1ngm0nk3y
Copy link
Contributor

@c0d1ngm0nk3y c0d1ngm0nk3y commented Feb 28, 2023

We would like to propose some enhancement to the run image resolution.

A possible implementation: buildpacks/lifecycle#1024

platform.md Outdated Show resolved Hide resolved
@natalieparellano
Copy link
Member

@c0d1ngm0nk3y @pbusko thanks for this! Is it possible you could fix the DCO? I think you need to use Signed-off-by instead of (or in addition to) Co-authored-by.

Co-authored-by: Ralf Pannemans <ralf.pannemans@sap.com>
Co-authored-by: Pavel Busko <pavel.busko@sap.com>
Signed-off-by: Ralf Pannemans <ralf.pannemans@sap.com>
@samj1912
Copy link
Member

samj1912 commented Mar 9, 2023

@natalieparellano could you help retarget this to an appropriate branch?

@natalieparellano
Copy link
Member

natalieparellano commented Mar 9, 2023

@samj1912 sounds good. Should we be guarding this change in behavior on a Platform API version in the lifecycle? Or should this be treated more like a bug-fix and back-ported to older platforms?

@natalieparellano natalieparellano changed the base branch from main to platform/0.12 March 9, 2023 21:47
platform.md Outdated Show resolved Hide resolved
Co-authored-by: Ralf Pannemans <ralf.pannemans@sap.com>
Signed-off-by: Ralf Pannemans <ralf.pannemans@sap.com>
@c0d1ngm0nk3y
Copy link
Contributor Author

What is missing for this to be merged?

@natalieparellano
Copy link
Member

I believe this now has enough votes. @buildpacks/toc any further thoughts?

@c0d1ngm0nk3y
Copy link
Contributor Author

I believe this now has enough votes. @buildpacks/toc any further thoughts?

???

@natalieparellano
Copy link
Member

natalieparellano commented May 2, 2023

I've put this on the agenda for this week's CNB Working Group. I don't see any controversy here, but I'd like clarity on this question:

Should we be guarding this change in behavior on a Platform API version in the lifecycle? Or should this be treated more like a bug-fix and back-ported to older platforms?

@natalieparellano
Copy link
Member

Just to circle back here, the consensus from Working Group is that this should be safe to treat as a bug-fix.

@natalieparellano
Copy link
Member

Merging as this has all required approvals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants