Skip to content
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

feat: Add driver selection args #153

Merged
merged 2 commits into from
Apr 8, 2024

Conversation

gmpinder
Copy link
Member

@gmpinder gmpinder commented Apr 6, 2024

There are 2 new args available that allow the user to specify which program to use for building and inspecting images. If the user doesn't provide an argument, the tool will determine which program to use like it has been.

Help text:

Build an image from a recipe

Usage: bluebuild build [OPTIONS] [RECIPE]

Arguments:
  [RECIPE]
          The recipe file to build an image

Options:
  -p, --push
          Push the image with all the tags.

          Requires `--registry`, `--username`, and `--password` if not building in CI.

  -c, --compression-format <COMPRESSION_FORMAT>
          The compression format the images will be pushed in

          [default: gzip]
          [possible values: gzip, zstd]

  -n, --no-retry-push
          Block `bluebuild` from retrying to push the image

      --retry-count <RETRY_COUNT>
          The number of times to retry pushing the image

          [default: 1]

  -f, --force
          Allow `bluebuild` to overwrite an existing Containerfile without confirmation.

          This is not needed if the Containerfile is in .gitignore or has already been built by `bluebuild`.

  -a, --archive <ARCHIVE>
          Archives the built image into a tarfile in the specified directory

      --registry <REGISTRY>
          The registry's domain name

  -v, --verbose...
          Increase logging verbosity

  -q, --quiet...
          Decrease logging verbosity

      --registry-namespace <REGISTRY_NAMESPACE>
          The url path to your base project images

          [aliases: registry-path]

  -U, --username <USERNAME>
          The username to login to the container registry

  -P, --password <PASSWORD>
          The password to login to the container registry

  -B, --build-driver <BUILD_DRIVER>
          Select which driver to use to build your image

          [possible values: buildah, podman, docker]

  -I, --inspect-driver <INSPECT_DRIVER>
          Select which driver to use to inspect images

          [possible values: skopeo, podman, docker]

  -h, --help
          Print help (see a summary with '-h')

@gmpinder gmpinder added the type: feature Brand new functionality, features, pages, workflows, endpoints, etc. label Apr 6, 2024
@gmpinder gmpinder added this to the v0.8.4 milestone Apr 6, 2024
@gmpinder gmpinder self-assigned this Apr 6, 2024
@gmpinder gmpinder linked an issue Apr 6, 2024 that may be closed by this pull request
Copy link
Member

@xynydev xynydev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "driver" a good or standard term for this?

@gmpinder
Copy link
Member Author

gmpinder commented Apr 8, 2024

Is "driver" a good or standard term for this?

Yeah I've seen this term for similar features. It used to be called Strategy but I didn't particularly like it. Took too long to type over and over.

@gmpinder gmpinder merged commit e9c96e2 into main Apr 8, 2024
3 checks passed
@gmpinder gmpinder deleted the 143-feat-allow-overriding-the-build-strategy branch April 8, 2024 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature Brand new functionality, features, pages, workflows, endpoints, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: allow overriding the build strategy
2 participants