Skip to content

[release-1.8] feat: bumping orchestrator plugins to 1.8.10 - #2646

Merged
openshift-merge-bot[bot] merged 2 commits into
redhat-developer:release-1.8from
lholmquist:release-1.8.6-orchestrator
Apr 14, 2026
Merged

[release-1.8] feat: bumping orchestrator plugins to 1.8.10#2646
openshift-merge-bot[bot] merged 2 commits into
redhat-developer:release-1.8from
lholmquist:release-1.8.6-orchestrator

Conversation

@lholmquist

Copy link
Copy Markdown
Member

Description

[release-1.8] feat: bumping orchestrtor plugins to 1.8.10

Which issue(s) does this PR fix or relate to

PR acceptance criteria

  • Tests
  • Documentation

How to test changes / Special notes to the reviewer

@rhdh-qodo-merge

rhdh-qodo-merge Bot commented Apr 14, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0)   📘 Rule violations (1)   📎 Requirement gaps (0)
📘\ ✧ Quality (1)

Grey Divider


Action required

1. Missing backstage-backend-auth-secret Secret 📘
Description
examples/orchestrator-cicd.yaml references the Secret backstage-backend-auth-secret but does not
define it anywhere in the example manifest set, so applying the example would fail with NotFound.
Example bundles must include stubs for referenced Secrets/ConfigMaps to be self-contained.
Code

examples/orchestrator-cicd.yaml[123]

+        - name: backstage-backend-auth-secret
Evidence
PR Compliance ID 1 requires that all referenced resources (including Secrets) are defined in the
same example set. The modified example manifest includes extraEnvs.secrets referencing
backstage-backend-auth-secret, but the file contains only ConfigMaps and a Backstage CR (no `kind:
Secret` for that name).

Rule 1: Include all dependent Kubernetes resources in example manifests
examples/orchestrator-cicd.yaml[1-123]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`examples/orchestrator-cicd.yaml` references a Secret named `backstage-backend-auth-secret` via `spec.application.extraEnvs.secrets`, but the example does not include a `Secret` manifest for it. This makes the example non-self-contained and can fail when users `kubectl apply -f` the example.

## Issue Context
The compliance rule requires example manifest bundles to include all referenced dependent resources (Secrets/ConfigMaps/etc.) in the same example set.

## Fix Focus Areas
- examples/orchestrator-cicd.yaml[111-123]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

extraEnvs:
secrets:
- name: backstage-backend-auth-secret No newline at end of file
- name: backstage-backend-auth-secret

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Action required

1. Missing backstage-backend-auth-secret secret 📘 Rule violation ✧ Quality

examples/orchestrator-cicd.yaml references the Secret backstage-backend-auth-secret but does not
define it anywhere in the example manifest set, so applying the example would fail with NotFound.
Example bundles must include stubs for referenced Secrets/ConfigMaps to be self-contained.
Agent Prompt
## Issue description
`examples/orchestrator-cicd.yaml` references a Secret named `backstage-backend-auth-secret` via `spec.application.extraEnvs.secrets`, but the example does not include a `Secret` manifest for it. This makes the example non-self-contained and can fail when users `kubectl apply -f` the example.

## Issue Context
The compliance rule requires example manifest bundles to include all referenced dependent resources (Secrets/ConfigMaps/etc.) in the same example set.

## Fix Focus Areas
- examples/orchestrator-cicd.yaml[111-123]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@rhdh-qodo-merge

Copy link
Copy Markdown

Review Summary by Qodo

Upgrade orchestrator plugins to version 1.8.10

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Upgrade orchestrator plugins from v1.8.9 to v1.8.10
• Update integrity hashes for all four orchestrator plugin packages
• Synchronize version updates across configuration and documentation files
• Update example configurations and installation documentation
Diagram
flowchart LR
  A["Orchestrator Plugins v1.8.9"] -->|"Upgrade to v1.8.10"| B["Updated Plugin Packages"]
  B -->|"Update hashes"| C["Configuration Files"]
  B -->|"Update references"| D["Documentation & Examples"]
  C --> E["ConfigMap & Install YAML"]
  D --> F["Docs & Example Files"]
Loading

Grey Divider

File Changes

1. bundle/rhdh/manifests/rhdh-default-config_v1_configmap.yaml ⚙️ Configuration changes +8/-8

Update orchestrator plugins to 1.8.10 in ConfigMap

• Updated four orchestrator plugin packages from v1.8.9 to v1.8.10
• Updated integrity SHA512 hashes for all plugin packages
• Affected plugins: orchestrator, orchestrator-backend-dynamic,
 scaffolder-backend-module-orchestrator-dynamic, orchestrator-form-widgets

bundle/rhdh/manifests/rhdh-default-config_v1_configmap.yaml


2. config/profile/rhdh/default-config/dynamic-plugins.yaml ⚙️ Configuration changes +9/-9

Upgrade orchestrator plugins in default config

• Bumped all four orchestrator plugin versions from 1.8.9 to 1.8.10
• Updated corresponding integrity hashes for package verification
• Maintains plugin configuration structure and dependencies

config/profile/rhdh/default-config/dynamic-plugins.yaml


3. dist/rhdh/install.yaml ⚙️ Configuration changes +8/-8

Update orchestrator plugins in install manifest

• Updated four orchestrator plugin package versions to 1.8.10
• Updated all associated integrity SHA512 hashes
• Synchronized with ConfigMap changes for consistency

dist/rhdh/install.yaml


View more (3)
4. docs/orchestrator.md 📝 Documentation +5/-5

Update orchestrator plugin version in documentation

• Updated orchestrator plugin version reference from v1.8.9 to v1.8.10
• Updated all four plugin package versions in code examples
• Maintains documentation structure and installation instructions

docs/orchestrator.md


5. examples/orchestrator-cicd.yaml ⚙️ Configuration changes +5/-5

Upgrade orchestrator plugins in CI/CD example

• Updated all four orchestrator plugin packages to v1.8.10
• Maintains plugin configuration and dependencies structure
• Adds newline at end of file for consistency

examples/orchestrator-cicd.yaml


6. examples/orchestrator.yaml ⚙️ Configuration changes +4/-4

Upgrade orchestrator plugins in example configuration

• Updated all four orchestrator plugin packages from v1.8.9 to v1.8.10
• Maintains plugin configuration and dependency references
• Adds newline at end of file for consistency

examples/orchestrator.yaml


Grey Divider

Qodo Logo

@rhdh-qodo-merge rhdh-qodo-merge Bot added documentation Improvements or additions to documentation enhancement New feature or request labels Apr 14, 2026
Co-authored-by: lholmquist <lholmquist@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

@sonarqubecloud

Copy link
Copy Markdown

@openshift-ci openshift-ci Bot added the lgtm label Apr 14, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit ae1c026 into redhat-developer:release-1.8 Apr 14, 2026
3 checks passed
lholmquist added a commit to lholmquist/rhdh-operator that referenced this pull request Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants