Gpg workflow#18
Merged
Merged
Conversation
abhishuraina
previously approved these changes
Jan 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔐 GPG Key Generation Workflow
This workflow automates the generation and distribution of GPG keys for signing New Relic Infrastructure packages.
✨ Features
🔑 Automated GPG Key Generation
Creates RSA 4096-bit keys with SHA256 hashing for package signing
📦 Dual Secret Storage
Private Keys stored in GitHub Organization Secrets:
OHAI_GPG_PRIVATE_SHA256- 🔄 Current (overwritten on each run)OHAI_GPG_PRIVATE_SHA256_<timestamp>- 📚 Historical backup📄 Dual Public Key Storage
Repository Structure:
gpg/keys/current/newrelic_rpm_key_current.gpg- 🔄 Current (overwritten)gpg/keys/new/newrelic_rpm_key_<timestamp>.gpg- 📚 Historical backup🛡️ Security Features
shred(10-pass overwrite) +rmGpgKeysOHAI)📝 Audit Trail
Optional reason input for documentation and compliance tracking
🚀 Triggers
📋 Key Format
Public keys exported in ASCII-armored format for easy viewing and distribution
🎯 Use Cases
OHAI_GPG_PRIVATE_SHA256secretgpg/keys/current/