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

Increase Build Plan Flexibility #82

Merged
merged 5 commits into from Jun 17, 2020
Merged

Conversation

nebhale
Copy link
Contributor

@nebhale nebhale commented May 28, 2020

Signed-off-by: Ben Hale <bhale@vmware.com>
@nebhale nebhale requested a review from a team as a code owner May 28, 2020 20:57
@hone
Copy link
Member

hone commented Jun 3, 2020

I think there's probably a way we can make it interoperate with the old plan. We could in the new world autocreate a version key in metadata for you. You do run the risk of it conflicting I suppose.

This change adds a statement about the lifecycle ensuring compatibility.

Signed-off-by: Ben Hale <bhale@vmware.com>
@nebhale
Copy link
Contributor Author

nebhale commented Jun 4, 2020

@hone Addressed in 9875b17

This change adds a statement about the change to the BOM schema to demote the
version key to match the buildpack plan.

Signed-off-by: Ben Hale <bhale@vmware.com>
@nebhale nebhale requested a review from hone June 5, 2020 21:04
nebhale added a commit to buildpacks/libcnb that referenced this pull request Jun 5, 2020
This change updates the library to remove the version field from the build
plan and buildpack plan in preparation for
buildpacks/rfcs#82.

Signed-off-by: Ben Hale <bhale@vmware.com>
nebhale added a commit to paketo-buildpacks/libpak that referenced this pull request Jun 5, 2020
This change updates the library to remove the version field from the build
plan and buildpack plan in preparation for
buildpacks/rfcs#82.

Signed-off-by: Ben Hale <bhale@vmware.com>
@hone
Copy link
Member

hone commented Jun 10, 2020

I'd love to get some input from buildpack authors like those from the Paketo team (@dwillist), Google (@dgageot @lukasberger), and Heroku (@danielleadams @Malax) at least since this impacts you the most.

Signed-off-by: Ben Hale <bhale@vmware.com>
@nebhale nebhale requested a review from hone June 10, 2020 19:18
@nebhale
Copy link
Contributor Author

nebhale commented Jun 10, 2020

Final Comment Period with merge disposition, closing on 17 June, 2020.

@danielleadams
Copy link
Member

Looked over this and discussed it with @hone. The Heroku buildpacks aren't using version, so this seems fine to move forward with.

Copy link
Member

@hone hone left a comment

Choose a reason for hiding this comment

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

I always have to look up if version is in provides or requires, so removing this key for now will make the build plan more approachable to newer users.

Signed-off-by: Ben Hale <bhale@vmware.com>

Co-authored-by: Terence Lee <hone02@gmail.com>
nebhale added a commit that referenced this pull request Jun 17, 2020
[#82]

Signed-off-by: Ben Hale <bhale@vmware.com>
@nebhale nebhale merged commit b29c749 into master Jun 17, 2020
@nebhale nebhale deleted the increase-build-plan-flexibility branch June 17, 2020 19:10
nebhale added a commit to buildpacks/spec that referenced this pull request Jun 24, 2020
This change implements the updates from buildpacks/rfcs#82.

[resolves #91]

Signed-off-by: Ben Hale <bhale@vmware.com>
nebhale added a commit to buildpacks/spec that referenced this pull request Jun 25, 2020
This change implements the updates from buildpacks/rfcs#82.

[resolves #91]

Signed-off-by: Ben Hale <bhale@vmware.com>
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