carvel-dev / carvel-dev/carvel
Mac developer certification for Carvel tools
- Dominant language
- HTML
- Stars
- 408
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
A few Carvel tools are required to use the Cloud Native Runtimes (CNR) CLI (ytt, kapp, and kbld). I got some feedback from someone who was going through the Cloud Native Runtimes install process that they had to go through the Mac process of going to System Preferences, Security and Privacy, and click "allow anyway" to be able to open the tools. I know there is some kind of option to get a developer certification for products so that users won't get the security notification before opening Carvel tools, is this something your team has considered? Since we'll have more users coming to the Carvel tools through CNR installation, this is some feedback I wanted to pass on.
Contributor guide
Research direction
No files or tests are named. Start by reviewing the distribution and release process for ytt, kapp, and kbld, along with the Cloud Native Runtimes installation path. Done means determining a supported Mac certification approach that prevents users from needing to select “allow anyway” before opening the tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100