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

RFC: Rebase by Image Digest Reference #262

Merged
merged 6 commits into from
Jan 5, 2023

Conversation

joeybrown-sf
Copy link
Contributor

@joeybrown-sf joeybrown-sf commented Dec 8, 2022

@buildpack-bot
Copy link
Member

Maintainers,

As you review this RFC please queue up issues to be created using the following commands:

/queue-issue <repo> "<title>" [labels]...
/unqueue-issue <uid>

Issues

(none)

Signed-off-by: Joey Brown <brown.joseph@salesforce.com>
Signed-off-by: Joey Brown <brown.joseph@salesforce.com>
1. `lifecycle rebase my-repo/foo:v4`

Here are some examples of currently invalid rebase commands using **digest references**:
1. `lifecycle rebase my-repo/foo@sha256:1234 myrepo/foo`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if introducing an explicit -previous-image flag would make things clearer:
lifecycle rebase -previous-image my-repo/foo@sha256:1234 myrepo/foo
If -previous-image is not provided we infer it from the first argument, just like analyzer.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@natalieparellano Do you think I should reframe this RFC around this "previous-image" flag?

A new title might be Add optional "-previous-image" flag to lifecycle rebase.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joeybrown-sf up to you - personally I think the title you have still applies here and the flag is more of an implementation detail. Do we like this suggestion? It seems clearer to me, but maybe others feel differently. @jabrown85 do you have any thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think an explicit argument is fine here. I agree it is an implementation detail of the RFC as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 this makes sense to me.

@hone
Copy link
Member

hone commented Dec 13, 2022

@joeybrown-sf unless there are objections, can you update the examples with the -previous-image flag and also add the changes to pack?

@natalieparellano
Copy link
Member

@jabrown85 would you be interested in stewarding this one?

@natalieparellano natalieparellano added status/needs-steward scope/team RFC scoped to a sub-team as opposed to the entire project. team/implementation spec/platform labels Dec 15, 2022
@jabrown85
Copy link
Contributor

Sure @natalieparellano! I got this one

@joeybrown-sf
Copy link
Contributor Author

@joeybrown-sf unless there are objections, can you update the examples with the -previous-image flag and also add the changes to pack?

@hone Are you asking for one more RFC PR? Very similar to this one, except different labels? Or something else?

@hone
Copy link
Member

hone commented Jan 4, 2023

@hone Are you asking for one more RFC PR? Very similar to this one, except different labels? Or something else?

Just updating the current RFC.

Signed-off-by: Joey Brown <brown.joseph@salesforce.com>
Signed-off-by: Joey Brown <brown.joseph@salesforce.com>
Signed-off-by: Joey Brown <brown.joseph@salesforce.com>
@jabrown85
Copy link
Contributor

Voting scheduled to end January 12th

@jabrown85
Copy link
Contributor

Because this is a team RFC - we have unanimously agreed to forgo the final comment period.

jabrown85 added a commit that referenced this pull request Jan 5, 2023
[#262]

Signed-off-by: Jesse Brown <jabrown85@gmail.com>
@jabrown85 jabrown85 merged commit 59a833d into buildpacks:main Jan 5, 2023
@joeybrown-sf joeybrown-sf deleted the rebase/digest-ref branch January 5, 2023 20:20
jabrown85 added a commit to buildpacks/spec that referenced this pull request Jan 23, 2023
Handles buildpacks/rfcs#262

Signed-off-by: Jesse Brown <jabrown85@gmail.com>

Signed-off-by: Jesse Brown <jabrown85@gmail.com>
jjbustamante pushed a commit that referenced this pull request Feb 13, 2023
[#262]

Signed-off-by: Jesse Brown <jabrown85@gmail.com>

Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
jjbustamante pushed a commit to jjbustamante/cnb-spec that referenced this pull request Mar 27, 2023
Handles buildpacks/rfcs#262

Signed-off-by: Jesse Brown <jabrown85@gmail.com>

Signed-off-by: Jesse Brown <jabrown85@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants