-
Notifications
You must be signed in to change notification settings - Fork 22
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
bake: support composable attributes #514
Conversation
aa2455e
to
733f698
Compare
733f698
to
8c24017
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
8c24017
to
068b0dc
Compare
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.
Looks good. I just had one question. I wanted to make sure that mixing the two styles worked correctly.
// convert to composable attributes: https://github.com/docker/buildx/pull/2758 | ||
for (const name in definition.target) { | ||
const target = definition.target[name]; | ||
if (target['cache-from'] && Array.isArray(target['cache-from'])) { |
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.
I think this means that you can mix the csv style with the composable style but I just wanted to make sure I was reading this right.
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.
It means we always want composable attributes so if csv values are passed we convert them to composable attributes.
I'm merging this one and will open a follow-up to handle attestations related to docker/buildx#2848. |
fixes #503
This adds support for composable attributes with backward compatibility for csv syntax.