Skip to content

pxrecipe: Add the push artifact and resolve the build tag in recipes before rendering - #12

Open
bensallen wants to merge 1 commit into
olcf:masterfrom
bensallen:pxrecipe_push
Open

pxrecipe: Add the push artifact and resolve the build tag in recipes before rendering#12
bensallen wants to merge 1 commit into
olcf:masterfrom
bensallen:pxrecipe_push

Conversation

@bensallen

Copy link
Copy Markdown
Contributor

Add a push artifact that commits the working container and pushes it to a registry with buildah push. A bare string sets the destination registry or a map accepts registry, image, tag, and format. image and tag default to the recipe name and build tag. The push tag argument takes either a single tag or a list of tags.

The build tag is now resolved in Recipe.init instead of in build(), making it available as {{tag}} when the recipe is rendered. It can now be used anywhere in a recipe, including artifact filenames and push tags.

show adds the same --tag flag so a recipe using {{tag}} can be inspected. The default tag moves to a module level default_tag() and is cached, so merged sub-recipes share one tag and git is only consulted once.

With the tag known up front, the osrelease step no longer needs placeholders in show output and render real values.

Also in osrelease, if specifying a IMAGE_ID or IMAGE_VERSION override in the recipe it is now explicitly ignored with a warning. Matches previous behavior.

…before rendering

Add a `push` artifact that commits the working container and pushes it
to a registry with `buildah push`. A bare string is the destination
registry or a map accepts `registry`, `image`, `tag`, and
`format`. `image` and `tag` default to the recipe name and build tag.
The push `tag` argument takes either a single tag or a list of tags.

The build tag is now resolved in Recipe.__init__ instead of in
build(), making it available as {{tag}} when the recipe is rendered.
It can now be used anywhere in a recipe, including artifact filenames
and push tags.

`show` grows the same --tag flag so a recipe using {{tag}} can be inspected.
The default tag moves to a module level default_tag() and is cached, so merged
sub-recipes share one tag and git is only consulted once.

With the tag known up front, the osrelease step no longer
needs placeholders in `show` output and render real values.

Also in osrelease, if specifying a IMAGE_ID or IMAGE_VERSION override
in the recipe it is now explicitly ignored with a warning. Matches
previous behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant