NO-ISSUE: Add AUTHFILE option to make image

[umohnani8]

When building the mco image, add an AUTHFILE check to allow users to specify a different file from the default one for the authentication to be used during the build process.

This is something I kept having to change manually because I use a different location for my openshift auth and not the default one that podman looks at.

- What I did
Add AUTHFILE option to make image to allow specifying a file path for the auth needed during build

- How to verify it
run make image AUTHFILE=path/to/auth file and the podman build command outputed should have --authfile=path/you/specified

- Description for the changelog
Add AUTHFILE option to make image to allow specifying a file path for the auth needed during build

[umohnani8]

/retest

[openshift-ci-robot]

@umohnani8: This pull request explicitly references no jira issue.

In response to this:

When building the mco image, add an AUTHFILE check to allow users to specify a different file from the default one for the authentication to be used during the build process.

This is something I kept having to change manually because I use a different location for my openshift auth and not the default one that podman looks at.

- What I did
Add AUTHFILE option to make image to allow specifying a file path for the auth needed during build

- How to verify it
run make image AUTHFILE=path/to/auth file and the podman build command outputed should have --authfile=path/you/specified

- Description for the changelog
Add AUTHFILE option to make image to allow specifying a file path for the auth needed during build

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.

[isabella-janssen]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, umohnani8

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 [umohnani8]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f0d60f5 and 2 for PR HEAD 3ac848a in total

[openshift-ci]

@umohnani8: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	3ac848a	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade-out-of-change	3ac848a	link	false	/test e2e-azure-ovn-upgrade-out-of-change

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 53cdf40 and 1 for PR HEAD 3ac848a in total

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.19.0-202501071907.p0.g599f6cd.assembly.stream.el9.
All builds following this will include this PR.