You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a project is deployed to GitHub, we add the credentials and associate them with the owner of the credentials. While this is helpful to project collaborators to identify the owner of a credential in the project.yaml, we also expose identifiable information via GitHub, especially when the repo is public. This leaves us with a few options:
Mask the email address of the credential owner
Allow users to decide if they want the credential owner specified in the project.yaml
athe ). If credential owner is required in the project.yaml, we should consider restricting Syncs to private repo.
The text was updated successfully, but these errors were encountered:
When a project is deployed to GitHub, we add the credentials and associate them with the owner of the credentials. While this is helpful to project collaborators to identify the owner of a credential in the project.yaml, we also expose identifiable information via GitHub, especially when the repo is public. This leaves us with a few options:
athe ). If credential owner is required in the project.yaml, we should consider restricting Syncs to private repo.
The text was updated successfully, but these errors were encountered: