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

Modernize Buildah sample build strategy #1001

Conversation

SaschaSchwarze0
Copy link
Member

Changes

I am changing the recently added registry configuration related parameters to arrays. I am adding build-arg support. I am using registries-insecure to also define whether tlsVerify on push should be set to false. And I am writing error details when the context dir or the Dockerfile do not exist.

Fixes #988

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

Release Notes

action required: The Buildah sample build strategy now supports build-args. The registry related parameters were changed to arrays in favor of comma-separated strings. You need to update your builds accordingly.

@SaschaSchwarze0 SaschaSchwarze0 added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 6, 2022
Copy link
Member

@gabemontero gabemontero left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@@ -17,49 +17,158 @@ spec:
- |
set -euo pipefail

echo "Creating registries config file..."
# Parse parameters
Copy link
Member

Choose a reason for hiding this comment

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

not asking as part of this PR, but I'm curious what would happen if you extracted the bash from this file, put it in a .sh file, and ran shellcheck against it

Copy link
Member Author

Choose a reason for hiding this comment

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

I had to do this because it failed as I had too much "s at one place. :-) But yeah, I further extended it after this. Would somehow be nice to get the inline script validated.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 7, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2022
@openshift-merge-robot openshift-merge-robot merged commit ae8d259 into shipwright-io:main Feb 7, 2022
@SaschaSchwarze0 SaschaSchwarze0 deleted the sascha-988-update-buildah branch February 16, 2022 10:38
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.9.0 milestone Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note-action-required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update BuildAh build strategy
3 participants