Skip to content

Conversation

@mrrajan
Copy link
Contributor

@mrrajan mrrajan commented Aug 4, 2025

As RHSSO operator reached EOL in June 2025, updated steps to configure Red Hat Build of Keycloak for RHTPA.

Summary by Sourcery

Update the admin guide to configure Red Hat Build of Keycloak for RHTPA, replacing all references and setup instructions for the deprecated RHSSO operator.

Documentation:

  • Replace RHSSO operator references with Red Hat Build of Keycloak (RHBK) in the infrastructure documentation
  • Update setup steps, container image names, environment variables, and configuration examples to use RHBK

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Aug 4, 2025

Reviewer's Guide

Documentation updated to replace end-of-life RHSSO operator with Red Hat Build of Keycloak (RHBK) in the RHTPA infrastructure guide, adjusting all references, installation steps, and example configurations accordingly.

File-Level Changes

Change Details Files
Switch operator and references from RHSSO to Red Hat Build of Keycloak
  • Update operator installation and subscription steps to use RHBK
  • Replace CRD and resource names from RHSSO to Keycloak
  • Adjust CLI commands and endpoints for Keycloak
docs/book/modules/admin/pages/infrastructure.adoc
Revise configuration examples to match Keycloak
  • Update sample realm and client setup snippets
  • Replace RHSSO-specific properties in manifest examples with Keycloak equivalents
docs/book/modules/admin/pages/infrastructure.adoc

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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @mrrajan - I've reviewed your changes and they look great!

Blocking issues:

  • Detected a Generic API Key, potentially exposing access to various services and sensitive operations. (link)
  • Detected a Generic API Key, potentially exposing access to various services and sensitive operations. (link)
Prompt for AI Agents
Please address the comments from this code review:
## Security Issues

### Issue 1
<location> `docs/book/modules/admin/pages/infrastructure.adoc:543` </location>

<issue_to_address>
**security (generic-api-key):** Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

*Source: gitleaks*
</issue_to_address>

### Issue 2
<location> `docs/book/modules/admin/pages/infrastructure.adoc:616` </location>

<issue_to_address>
**security (generic-api-key):** Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

*Source: gitleaks*
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Signed-off-by: mrrajan <[email protected].>
@mrrajan mrrajan force-pushed the doc_update_keycloak branch from d63b2e3 to e09ad6e Compare August 4, 2025 09:21
@mrrajan mrrajan force-pushed the doc_update_keycloak branch from d4d83ca to e6fae3e Compare August 5, 2025 12:26
@codecov
Copy link

codecov bot commented Aug 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.26%. Comparing base (c8f7067) to head (e6fae3e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1909   +/-   ##
=======================================
  Coverage   68.25%   68.26%           
=======================================
  Files         367      367           
  Lines       23216    23216           
  Branches    23216    23216           
=======================================
+ Hits        15847    15848    +1     
  Misses       6488     6488           
+ Partials      881      880    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants