crc 1.3.0 (new formula)

[cblecker]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[fxcoudert]

Looking at the webpage, I'm wondering about the additional constraints on this software:

Each released crc binary expires 30 days after the release due to certificates embedded in the Openshift cluster.

and

To use these binaries, please follow the instructions at https://cloud.redhat.com/openshift/install/crc/installer-provisioned to obtain the needed pull-secret

I'm wondering whether it makes sense for us shipping software with such restrictions.

[cblecker]

@fxcoudert any update on this? :)

[SMillerDev]

@Homebrew/core I think those restrictions mean that this formula is better suited for a personal tap. Any other opinions?

[iMichka]

If it means that someone needs to update the software here each 30 days, I would rather have it in a tap.

[MikeMcQuaid]

@cblecker Can you elaborate on the above restrictions when you get a chance? Thanks!

[claui]

If I understand the website correctly, the program now auto-updates certificates without needing recompilation.

The restriction quoted by @fxcoudert seems to be outdated and was corrected on the website a few days ago.

[cblecker]

That is correct. The 30 day restriction was technical (certificate renewals internal to the virtual cluster), and has since been fixed. The current version (1.3.0) does not have this restriction.

[MikeMcQuaid]

Thanks again so much for your contribution! Without people like you submitting PRs we couldn't run this project. You rock, @cblecker!