Deprecate user building features
- Dominant language
- Go
- Stars
- 927
- Forks
- 387
- Avg merge
- 15h 5m
- Merged PRs (30d)
- 36
Description
### Requirement
As we're providing feature parity between `IntegrationProfile` and the old `IntegrationPlatform` (#6705) we should remove the following features:
- builder trait: move builder properties to camel trait instead
- integration repositories: only inherit those available in the profile.
We must introduce a deprecation notice to enable future removal. We want to only enable certain build features via an administrative role (for example, via the creation of profiles).
Beside those we should enable the following policies in the profile (and default env var):
- enable Quarkus native: to make this option available via profile only
- quarkus images to use: use only the one provided in the profile (via allowlist)
- base images: use only the one provided in the profile (via allowlist)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the IntegrationProfile and IntegrationPlatform implementations and the existing builder, camel trait, and integration repository handling. Trace how profile policies and environment defaults are applied. Done means the listed user-building features are deprecated, profile repositories are restricted, and native, Quarkus image, and base-image policies use profile allowlists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, build-system, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100