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
If this API key is harmless, you can ignore this issue. If not, we would advise to move the secret out of the git repository by either injecting it via the environment or even better, by using a tool such as AWS Secrets Manager to inject the secrets at run-time. After that, it should be possible to invalidate the current secret and regenerate a new one.
The text was updated successfully, but these errors were encountered:
Find more live information in Aikido here: https://app.aikido.dev/queue?sidebarIssue=2485325&groupId=6798&sidebarIssueTask=580898&sidebarTab=tasks
Scope
This task includes issues in the following code repository:
TLDR
We detected secret *****e517 in the git history of the repository. The secret was found in proto/buf.yaml.
View commit:
permify/proto/buf.yaml
Line 6 in 72abba6
How to fix
If this API key is harmless, you can ignore this issue. If not, we would advise to move the secret out of the git repository by either injecting it via the environment or even better, by using a tool such as AWS Secrets Manager to inject the secrets at run-time. After that, it should be possible to invalidate the current secret and regenerate a new one.
The text was updated successfully, but these errors were encountered: