You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the GitHub App configuration page (https://github.com/organizations/[owner]/settings/apps/[app name]) and throughout GitHub’s official documentation, the .pem file that a GitHub app provides is referred to as a "private key". The GitHub Terraform provider, however, currently uses the variable name GITHUB_APP_PEM_FILE instead of GITHUB_APP_PRIVATE_KEY.
While functionally equivalent, this inconsistency makes knowledge transfer more difficult because:
Users must manually confirm that GITHUB_APP_PEM_FILE refers to the private key rather than another GitHub App credential.
Other GitHub tools, such as GitHub Actions (actions/create-github-app-token), use private-key, leading to unnecessary confusion.
Using GitHub’s native terminology improves clarity and reduces onboarding friction.
Proposal
Introduce GITHUB_APP_PRIVATE_KEY as the preferred variable name.
Continue supporting GITHUB_APP_PEM_FILE as a deprecated alias for backward compatibility.
This change would ensure consistency across GitHub’s ecosystem while maintaining existing behavior for current users.
Could this improvement be considered?
SDK Version
No response
API Version
No response
Relevant log output
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the need
On the GitHub App configuration page (
https://github.com/organizations/[owner]/settings/apps/[app name]
) and throughout GitHub’s official documentation, the .pem file that a GitHub app provides is referred to as a "private key". The GitHub Terraform provider, however, currently uses the variable nameGITHUB_APP_PEM_FILE
instead ofGITHUB_APP_PRIVATE_KEY
.While functionally equivalent, this inconsistency makes knowledge transfer more difficult because:
private-key
, leading to unnecessary confusion.Proposal
This change would ensure consistency across GitHub’s ecosystem while maintaining existing behavior for current users.
Could this improvement be considered?
SDK Version
No response
API Version
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: