RHTAPINST-186: GitHub Release Action vs. Container Image

[otaviof]

Fixing buildah GitHub Action error, and skipping container build in GHA given we need credentials to fetch Red Hat images.

[otaviof]

/hold

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[otaviof]

/hold cancel

[openshift-ci-robot]

@otaviof: This pull request references RHTAPINST-186 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

Fixing buildah GitHub Action error, and skipping container build in GHA given we need credentials to fetch Red Hat images.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[otaviof]

/retest

[otaviof]

/retest

[jduimovich]

This is giid. You cannot grab a secret in an action, it needs to be the workflow.
Change looks good to me (I made the same ones)

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jduimovich, otaviof

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:

• OWNERS [jduimovich,otaviof]

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

[otaviof]

/retest

[xinredhat]

/lgtm

[xinredhat]

/cherry-pick release-1.3

[openshift-cherrypick-robot]

@xinredhat: new pull request created: #342

In response to this:

/cherry-pick release-1.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.