Conversation
Signed-off-by: Joe Kutner <jpkutner@gmail.com> wip wip wip wip
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
Signed-off-by: Terence Lee <hone02@gmail.com>
Signed-off-by: Terence Lee <hone02@gmail.com>
Signed-off-by: Terence Lee <hone02@gmail.com>
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
|
Updated based on discussion in working group. Changes include:
|
|
There is an unresolved question regarding how to tag multiple
One of the options, which I'm proposing as a solution, is to have a platform use two value to construct the full image tag: [[images]]
id = "myorg/gateway"
[[images]]
id = "myorg/service1"A user could then run: |
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
90d88e4 to
684f133
Compare
|
I've added an example using image id prefix/suffix as discussed. |
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
|
I've moved the metadata keys in to I've added |
| exclude = ["<string>"] | ||
|
|
||
| [[images]] | ||
| ref = "<string>" |
There was a problem hiding this comment.
Small issue with ref vs tag: only tags are valid in this field, and other kinds of ref are not valid.
E.g., gcr.io/example/myapp@sha256:2342ab... is not valid, because it's not possible to know the digest ahead of time.
|
|
||
| ```toml | ||
| [project] | ||
| id = "<string>" |
There was a problem hiding this comment.
Were we going to replace id/version with ref (or tag, noting my comment below), and then combine it with the individual refs and suffixs?
There was a problem hiding this comment.
i think i'm fine with that. i'd probably move to make it optional though (which means there's no required id or tag, which might be a problem).
| ```toml | ||
| [project] | ||
| id = "io.buildpacks.my-app" | ||
| version = "0.1" |
There was a problem hiding this comment.
Seems unusual to require a version to be checked into a git repo for project.toml to be valid. That breaks certain release strategies.
|
|
||
| ## Example: Monorepos | ||
|
|
||
| The `[[images]]` array of tables allows the buildpack lifecycle to generate more than one image per build. Each table in the array may contain configuration that defines a different image for different parts of the code. For example: |
There was a problem hiding this comment.
clarify per pack build, not lifecycle build
|
From @jonjohnsonjr, Julia also has a Project.toml. |
|
Closing in favor of #32. We'll open a new RFC for |
Readable