feat: Allow users to have protected projects for safe shared registry operations#6635
Open
ntkathole wants to merge 1 commit into
Open
feat: Allow users to have protected projects for safe shared registry operations#6635ntkathole wants to merge 1 commit into
ntkathole wants to merge 1 commit into
Conversation
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6635 +/- ##
==========================================
+ Coverage 45.75% 45.81% +0.05%
==========================================
Files 414 414
Lines 49701 49750 +49
Branches 7087 7093 +6
==========================================
+ Hits 22739 22791 +52
+ Misses 25377 25361 -16
- Partials 1585 1598 +13
... and 2 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Adds the ability to mark a Feast project as protected - shielding it from teardown and delete operations and hiding it from project listings.
Add
feast.dev/protected-project: "true"annotation to a FeatureStore CR - no CRD schema changes required. Remove the annotation to unprotect.