envoyproxy / envoyproxy/envoy-mobile
Formalize Credential Sharing
Open
build
distribution
no stalebot
- Dominant language
- Java
- Stars
- 566
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
Based on a slack conversation, it sounds like credential sharing for envoy-mobile is ad-hoc. We should move towards using an [Open Source 1Password Teams Account](https://github.com/1Password/1password-teams-open-source) a la CNCF best practices to bump our bus factor.
This is also a (soft) blocker for setting up a PyPI account for py-envoy-mobile as to minimize credential migrations down the line.
Contributor guide
Assessment
This issue has not been assessed yet.