Update ironbank build with latest docker context #67504
Conversation
The file `download.json` is replaced by `hardening_manifest.yaml`, which includes various pieces of information about the Iron Bank build.
pugnascotia
added
>enhancement
:Delivery/Packaging
|
Pinging @elastic/es-delivery (Team:Delivery) |
| value: "93dcc18adc78c65a028a84799ecf8ad40c936fdfc5f2a57b1acda5a8117fa82c" | ||
|
|
||
| # List of project maintainers | ||
| maintainers: |
There was a problem hiding this comment.
Should/could we use distro lists here?
There was a problem hiding this comment.
What would they be?
@nkammah any thoughts here?
There was a problem hiding this comment.
I don't see any mention in the doc on using distro lists - the different examples I've looked at in other projects uses individuals. If you're ok with it, let's stick to individuals for now.
|
@elasticmachine update branch |
| # Human-readable description of the software packaged in the image | ||
| org.opencontainers.image.description: "You know, for search." | ||
| # License(s) under which contained software is distributed | ||
| org.opencontainers.image.licenses: "${license}" |
There was a problem hiding this comment.
What will the value be for "${license}"
There was a problem hiding this comment.
It'll "Elastic-License".
| value: "93dcc18adc78c65a028a84799ecf8ad40c936fdfc5f2a57b1acda5a8117fa82c" | ||
|
|
||
| # List of project maintainers | ||
| maintainers: |
There was a problem hiding this comment.
I don't see any mention in the doc on using distro lists - the different examples I've looked at in other projects uses individuals. If you're ok with it, let's stick to individuals for now.
The file `download.json` is replaced by `hardening_manifest.yaml`, which includes various pieces of information about the Iron Bank build.
|
Backported to |
The file
download.jsonis replaced byhardening_manifest.yaml, whichincludes various pieces of information about the Iron Bank build.