SANDBOX-1769 | feature: type for "enabled integrations" in the config

[MikelAlejoBR]

Description

We want to be able to control the integrations that are displayed in the UI via the ToolchainConfig, and in order to do that we need to have a field that controls which integrations are enbaled and which are not.

Related PRs

• SANDBOX-1769 | feature: type for "enabled integrations" in the config #502
• SANDBOX-1769 | feature: "enabled integrations" builder for the tests toolchain-common#524
• SANDBOX-1769 | docs: design of the "enabled integrations" feature host-operator#1255
• SANDBOX-1769 | feature: definition of the "enabled integrations" in the CRD host-operator#1256
• SANDBOX-1769 | feature: expose "enabled integrations" in the UIConfig registration-service#590

Jira ticket

[SANDBOX-1769]

Checks

1. Did you run make generate target? yes/no

Yes.

3. Did make generate change anything in other projects (host-operator, member-operator)? yes/no

Yes.

5. In case of new CRD, did you the following? yes/no
   • make/generate.mk in this repository
   • resources/setup/roles/host.yaml in the sandbox-sre repository
   • PROJECT file: https://github.com/codeready-toolchain/host-operator/blob/master/PROJECT
   • CSV file: https://github.com/codeready-toolchain/host-operator/blob/master/config/manifests/bases/host-operator.clusterserviceversion.yaml

It is not a new CRD, but rather a change in an existing one.

6. In case other projects are changed, please provides PR links.
   • host-operator: https://github.com/codeready-toolchain/host-operator/pull/#
   • member-operator: https://github.com/codeready-toolchain/member-operator/pull/#

Will do as soon as I open them

Summary by CodeRabbit

• New Features
  • Added optional configuration to control integration visibility in the UI. When specified, only the listed integrations are displayed; when unset or empty, all integrations remain enabled.

[coderabbitai]

Walkthrough

A new optional configuration field enabledIntegrations of type string array is added to RegistrationServiceConfig. This field controls which integrations are visible or enabled in the UI, with nil or empty values treating all integrations as enabled. Updates span type definitions, API documentation, deepcopy implementations, and OpenAPI schema generation.

Changes

Cohort / File(s)	Summary
Type Definition and Documentation api/v1alpha1/toolchainconfig_types.go, api/v1alpha1/docs/apiref.adoc	Added EnabledIntegrations []string field to RegistrationServiceConfig struct with JSON annotation and documentation describing UI integration filtering behavior.
Generated Code api/v1alpha1/zz_generated.deepcopy.go, api/v1alpha1/zz_generated.openapi.go	Updated deepcopy logic to handle the new field via slice allocation and copy, and added corresponding OpenAPI schema property with x-kubernetes-list-type: set vendor extension.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a type/field for 'enabled integrations' configuration in ToolchainConfig.
Description check	✅ Passed	PR description covers main objectives, provides Jira ticket, and includes all required checklist items with appropriate responses.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud