carvel-dev / carvel-dev/kapp-controller

creator of PackageRepository CR should be able to specify which packages are imported

Open
#364 4 comments 0 reactions 0 assignees View on GitHub
carvel-accepted enhancement
Dominant language
Go
Stars
323
Forks
127
Avg merge
2d 16h
Merged PRs (30d)
4

Description

**Describe the problem/challenge you have**

Currently when PackageRepository CR is created all packages become available for use. Administrators (who create PkgRepo CRs) might be interested in locking down what particular PackageRepository imports into the cluster.

**Describe the solution you'd like**

Provide a filtering feature on PackageRepository CR for Packages and PackageMetadata that would allow somebody to specify what packages can be imported. I could see us supporting exact names, and wildcard name matches. I dont believe we should allow filtering by version.

Should there be a configurable default on kc to import nothing by default?

---
Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.