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.
Publishing a unit as an image with
brave publish
now allows for naming the exported images using the new bravetools image field syntax: <image_name>[/version][/arch].The exported image files now use the same format as bravetools image store for consistency, delimiting with underscore ("_") instead of the old legacy design that used a hypen ("-"). If no image string is provided, the default will be to export the unit as
unit_name/$timestamp
just like it is currently. This image_name/version will be preserved when the image file is imported withbrave import
.Since the
brave publish
command can export multiple units at once, you can provide multiple image names to apply to the exported images at the CLI. This can be done either by delimiting the image names with commas or by providing the "image_name" flag multiple times.Example:
Alternative syntax for labelling multiple exported images: