Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Secret-looking text in log output, ci logs redacted

Open
  • Is something wrong?
#1,311 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
ci-cd, security, testing

Research direction

Start with test/openshift/e2e/ginkgo/parallel/1-126_validate_declarative_webhook_secrets_test.go at the reported lines and inspect the CI output around the secret-related steps. Identify why secret-looking values are emitted in the logs, then verify the affected E2E tests complete without exposing sensitive-looking text.

Written by the indexing model from the issue text.

Description

This file contained potentially sensitive information and has been removed.

4479 │ GitOps Operator Parallel E2E Tests 1-126_validate_declarative_webhook_secrets does not remove webhook.github.secret when spec.webhookSecrets is never set on the Argo CD CR
4480 │ /go/src/github.com/redhat-developer/gitops-operator/test/openshift/e2e/ginkgo/parallel/1-126_validate_declarative_webhook_secrets_test.go:337
4481 │ 
4482 │   Timeline >>
4483 │   STEP: creating namespace 'gitops-e2e-test-8e0680d0-ef37' @ 09/22/26 14:46:23.37
4484 │   STEP: waiting for argocd-secret and operator-populated keys @ 09/22/26 14:46:23.665
4485 │   v1.Secret does not exists in ExistByName: argocd-secret secrets "argocd-secret" not found
4486 │   v1.Secret exists in ExistByName: argocd-secret
4487 │   HaveNonEmptyKeyValue - Key: admin.password  Have: $2a$10$qgx7N06h6GI/cTGcM1e8TeTZndItR9OqWGNRkOpxaB6Q/yNUELxHi
4488 │   STEP: writing webhook.github.secret on argocd-secret without spec.webhookSecrets @ 09/22/26 14:46:29.219
4489 │   Deleting Namespace gitops-e2e-test-8e0680d0-ef37
4490 │   << Timeline
4491 │ ------------------------------
4492 │ • [54.571 seconds]
4493 │ GitOps Operator Parallel E2E Tests 1-126_validate_declarative_webhook_secrets preserves webhook.github.secret after declarative sync when entire spec.webhookSecrets is cleared
4494 │ /go/src/github.com/redhat-developer/gitops-operator/test/openshift/e2e/ginkgo/parallel/1-126_validate_declarative_webhook_secrets_test.go:376
4495 │ 
4496 │   Timeline >>
4497 │   STEP: creating namespace 'gitops-e2e-test-c6260ab3-51af' @ 09/22/26 14:46:25.279
4498 │   STEP: waiting for argocd-secret and operator-populated keys @ 09/22/26 14:46:25.605
4499 │   v1.Secret does not exists in ExistByName: argocd-secret secrets "argocd-secret" not found
4500 │   v1.Secret exists in ExistByName: argocd-secret
4501 │   HaveNonEmptyKeyValue - Key: admin.password  Have: $2a$10$ENHDPsB0wqQdlFDJj/ltzOalUyi4tbpLsIxjkq5uJm/rneEYyvD4m
4502 │   STEP: merging spec.webhookSecrets: null so the field is unset (operator skips per-provider webhook cleanup) @ 09/22/26 14:46:38.91
4503 │   Deleting Namespace gitops-e2e-test-c6260ab3-51af
4504 │   << Timeline
Dominant language
Go
Stars
188
Forks
359
Avg merge
3d 12h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redhat-developer/gitops-operator

All issues in redhat-developer/gitops-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.