Skip to content

Chore: Add config provider and legacy support for config management#222

Closed
roguepikachu wants to merge 7 commits intokubevela:mainfrom
roguepikachu:fix/add-config-provider-cuex
Closed

Chore: Add config provider and legacy support for config management#222
roguepikachu wants to merge 7 commits intokubevela:mainfrom
roguepikachu:fix/add-config-provider-cuex

Conversation

@roguepikachu
Copy link
Copy Markdown
Contributor

@roguepikachu roguepikachu commented Dec 2, 2025

Description of your changes

Fixes #

I have:

  • Read and followed KubeVela's contribution process.
  • Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
  • Run make reviewable to ensure this PR is ready for review.
  • Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer


Summary by cubic

Add a new config provider to create, read, list, and delete configs stored as Kubernetes Secrets. Also adds legacy support so existing op-based workflows keep working.

  • New Features

    • New internal provider: config with actions create/read/list/delete.
    • Stores configs in Secrets under key input-properties with labels:
      • config.oam.dev/catalog=velacore-config
      • config.oam.dev/type= (optional; list can filter by template)
      • CUE templates for both providers:
        • provider: "config" (new)
        • provider: "op" (legacy)
      • Registered in the compiler and legacy provider registry.
      • Migration

        • No changes required. Legacy op-based steps continue to work; new workflows can use provider "config".
      • Written for commit 7b3f5cd. Summary will update automatically on new commits.

Signed-off-by: Ayush Kumar <ayushshyamkumar888@gmail.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented Dec 2, 2025

Codecov Report

❌ Patch coverage is 34.51327% with 148 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.78%. Comparing base (d7db9c4) to head (7b3f5cd).
⚠️ Report is 11 commits behind head on main.

Files with missing lines Patch % Lines
pkg/providers/config/config.go 7.27% 102 Missing ⚠️
pkg/providers/legacy/config/config.go 59.29% 28 Missing and 18 partials ⚠️

❌ Your patch status has failed because the patch coverage (34.51%) is below the target coverage (70.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #222      +/-   ##
==========================================
+ Coverage   62.49%   68.78%   +6.29%     
==========================================
  Files          62       64       +2     
  Lines        4415     5235     +820     
==========================================
+ Hits         2759     3601     +842     
+ Misses       1324     1261      -63     
- Partials      332      373      +41     
Flag Coverage Δ
e2etests 23.77% <34.51%> (?)
unit-test 61.81% <8.40%> (-0.68%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

roguepikachu and others added 6 commits December 2, 2025 15:35
Signed-off-by: Reetika Malhotra <malhotra.reetika25@gmail.com>
…ove read/list parameters

Signed-off-by: Reetika Malhotra <malhotra.reetika25@gmail.com>
Signed-off-by: Ayush Shyam Kumar <ayushshyam.official.888@gmail.com>
Signed-off-by: Ayush Shyam Kumar <ayushshyam.official.888@gmail.com>
Signed-off-by: Chaitanya Reddy Onteddu <co@guidewire.com>
…d save-list-to-configmap steps with detailed ConfigMap verification.

Signed-off-by: Chaitanyareddy0702 <chaitanyareddy0702@gmail.com>
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-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.

No issues found across 9 files

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.

3 participants