-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support local buildpacks and meta-buildpacks in libcnb-test (outdated) #590
Closed
Closed
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8ca33f4
Support local buildpacks and meta-buildpacks in libcnb-test
colincasey d2cd784
Ignore the target workspace dir
colincasey 67a9af2
Clean up error handling and docs
colincasey df125ca
Updated CHANGELOG.md
colincasey df58c3c
Updated integration tests
colincasey 2042df4
Update libcnb-test/src/pack.rs
colincasey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,4 +5,4 @@ id = "multiple-buildpacks/one" | |
version = "0.0.0" | ||
|
||
[[stacks]] | ||
id = "some-stack" | ||
id = "*" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,4 +5,4 @@ id = "multiple-buildpacks/two" | |
version = "0.0.0" | ||
|
||
[[stacks]] | ||
id = "some-stack" | ||
id = "*" |
31 changes: 31 additions & 0 deletions
31
libcnb-cargo/fixtures/multiple_buildpacks/meta-buildpacks/meta-two/buildpack.toml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
api = "0.8" | ||
|
||
[buildpack] | ||
id = "multiple-buildpacks/meta-two" | ||
name = "Meta-buildpack Test" | ||
version = "0.0.0" | ||
homepage = "https://example.com" | ||
description = "Official test example" | ||
keywords = ["test"] | ||
|
||
[[buildpack.licenses]] | ||
type = "BSD-3-Clause" | ||
|
||
[[order]] | ||
|
||
[[order.group]] | ||
id = "multiple-buildpacks/one" | ||
version = "0.0.0" | ||
|
||
[[order.group]] | ||
id = "multiple-buildpacks/two" | ||
version = "0.0.0" | ||
|
||
[[order.group]] | ||
id = "heroku/procfile" | ||
version = "2.0.0" | ||
optional = true | ||
|
||
[metadata] | ||
[metadata.extra] | ||
some_key = "some_value" |
11 changes: 11 additions & 0 deletions
11
libcnb-cargo/fixtures/multiple_buildpacks/meta-buildpacks/meta-two/package.toml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
[buildpack] | ||
uri = "." | ||
|
||
[[dependencies]] | ||
uri = "libcnb:multiple-buildpacks/one" | ||
|
||
[[dependencies]] | ||
uri = "libcnb:multiple-buildpacks/two" | ||
|
||
[[dependencies]] | ||
uri = "docker://docker.io/heroku/procfile-cnb:2.0.0" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,4 +5,4 @@ id = "single-buildpack" | |
version = "0.0.0" | ||
|
||
[[stacks]] | ||
id = "some-stack" | ||
id = "*" |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Question for maintainers, no action] More of a question for Manuel and Ed. This package is mostly exposed for re-use in our tooling. I would assume that we don't expect others to use these interfaces directly or do we?
Are we treating
libcnb-package
as a "true" cargo project with version guarantees, or is it more like this internal serde crate https://crates.io/crates/serde_derive_internals?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I'd thought the former, but I'm open to either really, as long as we're clear with potential external consumers of the create. Also at the moment with libcnb being pre-v1, we're bumping the major version most releases, so this mostly won't be an issue - and later once we go v1 I suspect
libcnb-package
will have settled down enough that we don't expect too much breakage.One thing to watch out for though - if we were to switch to being more relaxed about the major version for
libcnb-package
- we'd really have to switch to using hard version pins instead of ranges for intra-crate dependencies. ie:libcnb-cargo
would need to depend onlibcnb-package
version==1.2.3
not^1.2.3
. (We should perhaps make that switch regardless given our unified release versions approach.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@schneems Just to follow up here - we've now (a) switched to hard version pins in #644, (b) marked
libcnb-package
(and the newlibcnb-common
) as internal in their READMEs in #662.