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.

Sign up for GitHub

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

Jump to bottom

Kubernetes Secrets not detected. #703

Open
1 of 2 tasks
guettli opened this issue Jul 10, 2023 · 1 comment
Open
1 of 2 tasks

Kubernetes Secrets not detected. #703

guettli opened this issue Jul 10, 2023 · 1 comment
Labels
enhancement The issue is related to improving a certain aspect of the project. triaged The issue has been reviewed but has not been solved yet.

Comments

@guettli
Copy link

guettli commented Jul 10, 2023

  • I'm submitting a ...

    • bug report
    • feature request

  • What is the current behavior?

detect-secrets did not detect this secret:

apiVersion: v1
data:
  foo: |
    YWMzN2Iysd2h2s8HG463....
kind: Secret
metadata:
  name: foo
type: Opaque
  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Add above yaml file, and run detect-secrets.

  • What is the expected behavior?

I want above secret to get detected.

  • What is the motivation / use case for changing the behavior?

I don't want Kubernetes Secrets in my git repo.,

  • Please tell us about your environment:

    • detect-secrets Version: 1.4.0
    • Python Version: 3.10
    • OS Version: Linux
    • File type (if applicable): yaml

  • Other information
@geekNero
Copy link

I don't think Kubernetes secrets are supported as of yet

@lorenzodb1 lorenzodb1 added the pending The issue still needs to be reviewed by one of the maintainers. label Nov 17, 2023
@lorenzodb1 lorenzodb1 added triaged The issue has been reviewed but has not been solved yet. enhancement The issue is related to improving a certain aspect of the project. and removed pending The issue still needs to be reviewed by one of the maintainers. labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement The issue is related to improving a certain aspect of the project. triaged The issue has been reviewed but has not been solved yet.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@guettli @lorenzodb1 @geekNero