Skip to content

docs: document GCP project for hosted mint#2464

Draft
ifireball wants to merge 1 commit into
fullsend-ai:mainfrom
ifireball:cursor/document-hosted-mint-gcp-project
Draft

docs: document GCP project for hosted mint#2464
ifireball wants to merge 1 commit into
fullsend-ai:mainfrom
ifireball:cursor/document-hosted-mint-gcp-project

Conversation

@ifireball

Copy link
Copy Markdown
Member

Summary

  • Document the GCP project (it-gcp-konflux-dev-fullsend) and region where the fullsend team hosts the default public mint Cloud Function
  • Restructure the hosted mint section so the mint URL is labeled separately from the platform project details

Test plan

  • Doc-only change; no code or CI impact
  • Review hosted mint section for accuracy with platform operators

Made with Cursor

Record where the default public mint Cloud Function runs so platform
operators and SREs can find it without inferring from gcloud config.

Signed-off-by: Barak Korren <bkorren@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown

Site preview

Preview: https://e2a61287-site.fullsend-ai.workers.dev

Commit: 7c33546cff533b9c8d53a53cc9a9f33c3651e4b6

@fullsend-ai-review

fullsend-ai-review Bot commented Jun 21, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 8:26 AM UTC · Completed 8:34 AM UTC
Commit: 7c33546 · View workflow run →

@codecov

codecov Bot commented Jun 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

High

  • [sensitive data exposure] docs/guides/infrastructure/mint-administration.md:21 — The diff adds the GCP project name it-gcp-konflux-dev-fullsend and project number 855403973659 to a committed documentation file. The repository's AGENTS.md policy explicitly prohibits committing GCP project names, listing them as sensitive data alongside tokens and API keys: "Never commit secrets (tokens, API keys, PEM keys, gcloud credentials) or sensitive data (GCP project names, service account identifiers, Model Armor template names, internal hostnames). Use environment variables with no defaults for sensitive values."
    Remediation: Remove the GCP project name and project number from the documentation. If operators need to discover the hosted mint's GCP project, reference an environment variable or internal configuration source (e.g., "see the platform team's deployment runbook") rather than hard-coding the value in version-controlled files.

Low

  • [structural-consistency] docs/guides/infrastructure/mint-administration.md:23 — The label **Mint URL:** followed by an empty line and then a code block creates a terse introduction compared to other code block introductions in the file, which typically use full prose sentences.

Labels: PR modifies mint service documentation under docs/guides/infrastructure/.

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

See the review comment for full details.

The fullsend team operates a public hosted mint service. If your organization is enrolled, you can use it directly without deploying your own:
The fullsend team operates a public hosted mint service. If your organization is enrolled, you can use it directly without deploying your own.

**Platform GCP project:** The hosted mint currently runs in GCP project `it-gcp-konflux-dev-fullsend` (project number `855403973659`, region `us-central1`).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[high] sensitive data exposure

The diff adds the GCP project name it-gcp-konflux-dev-fullsend and project number 855403973659 to a committed documentation file. The repository's AGENTS.md policy explicitly prohibits committing GCP project names, listing them as sensitive data alongside tokens and API keys.

Suggested fix: Remove the GCP project name and project number from the documentation. If operators need to discover the hosted mint's GCP project, reference an environment variable or internal configuration source rather than hard-coding the value in version-controlled files.


**Platform GCP project:** The hosted mint currently runs in GCP project `it-gcp-konflux-dev-fullsend` (project number `855403973659`, region `us-central1`).

**Mint URL:**

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[low] structural-consistency

The label 'Mint URL:' followed by an empty line and then a code block creates a terse introduction compared to other code block introductions in the file, which typically use full prose sentences.

Suggested fix: Either remove the empty line between 'Mint URL:' and the code block, or integrate the URL into flowing prose.

@fullsend-ai-review fullsend-ai-review Bot added component/mint Token mint and cross-boundary credentials component/docs User-facing documentation labels Jun 21, 2026
@ifireball ifireball self-assigned this Jun 21, 2026

@rh-hemartin rh-hemartin left a comment

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.

Not sure why this is a draft, but LGTM. Which stuff do you want to add in addition to current changes?

@ifireball

Copy link
Copy Markdown
Member Author

Not sure why this is a draft, but LGTM. Which stuff do you want to add in addition to current changes?

All the bots jumped on this and said this is against our stated policy and might be a security risk, so I kept as draft for now.

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

Labels

component/docs User-facing documentation component/mint Token mint and cross-boundary credentials

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants