Skip to content

Conversation

@SequeI
Copy link
Contributor

@SequeI SequeI commented Jul 23, 2025

Summary by Sourcery

Upgrade the build environment to Go 1.24 and enforce strict FIPS compliance in the Dockerfile for the rhtas-operator image

New Features:

  • Enable strict FIPS compliance by using a FIPS-certified base image and enforcing FIPS mode

Enhancements:

  • Upgrade the Go toolset to version 1.24 in the RHTAS operator Dockerfile

@sourcery-ai
Copy link

sourcery-ai bot commented Jul 23, 2025

Reviewer's Guide

This PR upgrades the Go toolchain to v1.24 and pivots the operator image to a strict FIPS-compliant build by switching to FIPS-enabled base images, installing and configuring FIPS-approved crypto libraries, and updating related CI and module settings.

File-Level Changes

Change Details Files
Bump Go version to 1.24 and switch to FIPS-enabled base images
  • Update Dockerfile FROM line to use golang:1.24-fips image
  • Refresh go.mod/go.sum to require go1.24
  • Update CI workflows to run on Go 1.24
Dockerfile.rhtas-operator.rh
go.mod
go.sum
.github/workflows/ci.yaml
Install and configure FIPS-approved crypto libraries
  • Add installation steps for openssl-fips and crypto-policies
  • Enable strict FIPS mode via environment variables
  • Remove any non-FIPS algorithm packages
Dockerfile.rhtas-operator.rh
Adjust testing and linting for FIPS environment
  • Add FIPS-mode flag to test scripts
  • Skip or adapt tests that rely on non-FIPS ciphers
  • Update linter config to allow FIPS compliance checks
scripts/test.sh
.github/workflows/ci.yaml
.golangci.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@SequeI SequeI merged commit fc14a78 into release-1.2 Jul 23, 2025
16 checks passed
@SequeI SequeI deleted the asiek/1.2GoBump branch July 23, 2025 15:00
@osmman osmman added the enhancement New feature or request label Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants