Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secretless component quality levels move from alpha/beta/GA to community/trusted/certified #1347

Open
6 tasks
izgeri opened this issue Sep 29, 2020 · 0 comments

Comments

@izgeri
Copy link
Contributor

izgeri commented Sep 29, 2020

We defined certification levels (CLs) after Secretless had its 1.0 release, but we haven't moved Secretless from qualifying providers / connectors / config managers as alpha/beta/stable to using the new certification level community/trusted/certified nomenclature.

In this issue, we will update the Secretless README / internals to be clear about the certification levels of the internal components.

AC:

  • List all internal components with their certification levels in the README
  • Ensure all Community components have a README in their implementation folder that includes basic details about how to use the component
  • Ensure the README links to READMEs and/or doc pages for all components
  • Ensure the README is clear about the CLs of each component
  • If any docs pages need to be updated (for example, to say Trusted instead of Beta), a corresponding docs issue is filed and linked in this PR
  • (Optional) if any components are close to being a higher CL, file issues to do the work required to promote the CL of the component (e.g. for the generic HTTP connector)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant