Document gitapp-callback secret misconfiguration bug

[Copilot]

A code review identified that gitapp-callback deployment's init container checks for the wrong secret name (references githubStatusProxy.privateKeySecret.name instead of its own GitHub App private key secret).

Changes

• Provided detailed bug report for manual issue creation
• Unable to create GitHub issue programmatically due to missing API capabilities
• Documented affected lines (37, 151 in 32-gitapp-callback.yaml)
• Suggested fix: add privateKeySecret config under gitappCallback or default to githubApp.privateKeySecretName

Current Bug

# Line 37: Wrong secret reference
echo "Waiting for secret {{ .Values.githubStatusProxy.privateKeySecret.name }} to be available..."

# Line 82: Uses githubApp config
- name: GITHUB_APP_ID
  value: {{ .Values.githubApp.appId | quote }}

# Line 151: Wrong secret reference
secretName: {{ .Values.githubStatusProxy.privateKeySecret.name }}

The init container will wait indefinitely or fail to detect missing secrets since it's checking githubStatusProxy's secret instead of gitapp-callback's own GitHub App credentials.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[bwalsh]

done. documented shared secret