Skip to content

#3784 Document Unused Tokens - #3836

Open
Weltraumschaf wants to merge 1 commit into
secureCodeBox:mainfrom
Weltraumschaf:3784_document-tokens
Open

Weltraumschaf wants to merge 1 commit into
secureCodeBox:mainfrom
Weltraumschaf:3784_document-tokens

Conversation

@Weltraumschaf

Copy link
Copy Markdown
Member

So we have the names somewhere before deleting it. Just in case we need to restore them.

Description

Checklist

  • Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
  • Make sure that all your commits are signed-off and that you are added to the Contributors file.
  • Make sure that all CI finish successfully.
  • Optional (but appreciated): Make sure that all commits are Verified.

So we have the names somewhere before deleting it. Just in case we
need to restore them.

Signed-off-by: Sven Strittmatter <[email protected]>
@netlify

netlify Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deploy Preview for docs-securecodebox ready!

Name Link
🔨 Latest commit 99eaa5d
🔍 Latest deploy log https://app.netlify.com/projects/docs-securecodebox/deploys/6aa9575f3ee37d0008be8fd7
😎 Deploy Preview https://deploy-preview-3836--docs-securecodebox.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@Weltraumschaf Weltraumschaf added the documentation Improvements or additions to documentation label Sep 15, 2026
@Weltraumschaf Weltraumschaf moved this from Triage to To Review in secureCodeBox Sep 15, 2026
@sonarqubecloud

Copy link
Copy Markdown

Comment on lines +45 to +46
- `HELM_REGISTRY_PASSWORD`: 🤷‍♂️ Not found in any repo nor password manager.
- `HELM_REGISTRY_USERNAME`: 🤷‍♂️ Not found in any repo nor password manager.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i've intentionally removed the HELM_REGISTRY_ ones from the list as they are no longer used.
I've now also deleted the secrets

- `GPG_COMMITS_PRIVATE_KEY`: GPG private key for the secureCodeBoxBot used to sign Maven releases.
- `HELM_REGISTRY_PASSWORD`: 🤷‍♂️ Not found in any repo nor password manager.
- `HELM_REGISTRY_USERNAME`: 🤷‍♂️ Not found in any repo nor password manager.
- `PAT_WITH_ADMIN`: 🤷‍♂️ Not found in any repo nor password manager.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please just delete the token, we will never find out otherwise if its used

- **`SONAR_TOKEN`** — Token for SonarCloud.
- `CC_TEST_REPORTER_ID`: 🤷‍♂️ Not found in any repo nor password manager.
- `DOCKER_NAMESPACE`: Namespace for the DockerHub images. For the main repository this is *securecodebox*.
- `DOCKER_PASSWORD`: 🤷‍♂️ Not found in any repo nor password manager.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was probably used before we switched to DOCKER_TOKEN, pls just delete

- **`SCB_BOT_DOCU_ROULETTE_TOKEN`** — GitHub token for the documentation roulette (needs `org:read` permission).
- **`SCB_BOT_USER_TOKEN`** — GitHub token for the secureCodeBoxBot.
- **`SONAR_TOKEN`** — Token for SonarCloud.
- `CC_TEST_REPORTER_ID`: 🤷‍♂️ Not found in any repo nor password manager.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please just delete the secret, we will never find out otherwise if its used

@J12934

J12934 commented Sep 15, 2026

Copy link
Copy Markdown
Member

Sorry had a look over the changed and didn't read the PR description, but don't really get what we have by basically documenting something that we don't understand what it was used for.

Either it breaks and we have to investigate what broke or they are unused and everything is fine.
Not sure what benefits we get, having this in the repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

Status: To Review

Development

Successfully merging this pull request may close these issues.

2 participants