refactor: keep the PingMailer name, use OpenGovMail only as the org - #38
Merged
Merged
Conversation
Follow-up correction to #37. That PR renamed the project itself to `opengovmail`, but only the organisation moved — the project is still PingMailer. This restores the project name everywhere and keeps OpenGovMail strictly as the org/registry owner. - Go module: github.com/OpenGovMail/opengovmail -> github.com/OpenGovMail/pingmailer - Images: opengovmail-{api-server,dkim,smtp,certbot} -> pingmailer-{api-server,dkim,smtp,certbot}; ghcr.io/opengovmail/ owner unchanged - Helm: umbrella chart `opengovmail` -> `pingmailer`; template helper prefixes opengovmail-* -> pingmailer-*; default namespace back to `pingmailer` - Paths: mail-infra/{conf/opengovmail.yaml,services/opengovmail-config, images/opengovmail-*} and scripts/service/{start,stop}-opengovmail.sh renamed back to their pingmailer equivalents - Env vars: OPENGOVMAIL_{YAML_FILE,CONFIG} -> PINGMAILER_{YAML_FILE,CONFIG} - Docs, NOTES.txt and workflow comments say PingMailer for the project and OpenGovMail only for the org (chart maintainers, sources, registry) No Silver or LSFLK references return; those stay retired. Verified: `go build ./...` and `go vet ./...` clean; `helm lint` and `helm template` succeed for the umbrella and certbot charts; `bash -n` passes on every shell script; no case-insensitive match for silver, lsflk or `opengovmail-` remains in the tree.
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
2 participants
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.
Follow-up correction to #37.
That PR renamed the project to
opengovmail, but only the organisation moved. The project is still PingMailer. This restores the project name everywhere and keepsOpenGovMail/opengovmailstrictly as the org and registry owner.Silver and LSFLK naming stays retired — no
silverorlsflkreference returns.What changed
github.com/OpenGovMail/opengovmailgithub.com/OpenGovMail/pingmailerghcr.io/opengovmail/opengovmail-api-serverghcr.io/opengovmail/pingmailer-api-serverghcr.io/opengovmail/opengovmail-dkimghcr.io/opengovmail/pingmailer-dkimghcr.io/opengovmail/opengovmail-smtpghcr.io/opengovmail/pingmailer-smtpghcr.io/opengovmail/opengovmail-certbotghcr.io/opengovmail/pingmailer-certbotopengovmailpingmaileropengovmail-smtp.fullname, …pingmailer-smtp.fullname, …mail-infra/conf/opengovmail.yamlmail-infra/conf/pingmailer.yamlmail-infra/services/opengovmail-config/mail-infra/services/pingmailer-config/mail-infra/images/opengovmail-{dkim,smtp-rootless}/mail-infra/images/pingmailer-{dkim,smtp-rootless}/{start,stop}-opengovmail.sh{start,stop}-pingmailer.shOPENGOVMAIL_{YAML_FILE,CONFIG}PINGMAILER_{YAML_FILE,CONFIG}Unchanged — these are correctly the org: the registry owner
ghcr.io/opengovmail/, chartmaintainers(OpenGovMail,https://github.com/OpenGovMail), chartsources, and the repo URL owner.ghcr.io/opengovmail/raven-saslalso keeps its name; only its owner moved, since it is built in a separate repository (see the note in.github/workflows/docker-release.yaml).Verification
go build ./...andgo vet ./...cleanhelm lint+helm templatesucceed for the umbrella chart andmail-infra/helm/certbot-serverbash -npasses on every shell scriptsilver,lsflkoropengovmail-remains in the treeopengovmail-*names from refactor: rename PingMailer/Silver to OpenGovMail #37 are now orphaned. Cut a release sodocker-release.yamlpushespingmailer-{api-server,dkim,smtp}before anyone deploys from these values, and re-publishpingmailer-certbotandghcr.io/opengovmail/raven-saslfrom their own repos.OpenGovMail/pingmailer, which is what the Go module path and all doc URLs now assume.mail-infra/scripts/cert-manager-bootstrap.shand the certbot chart originally citedLSFLK/silver#325; refactor: rename PingMailer/Silver to OpenGovMail #37 repointed those atOpenGovMail/pingmailer#325, which is a different PR. Worth correcting or dropping the citation.opengovmail-smtp-*→pingmailer-smtp-*), so an in-placehelm upgraderecreates objects rather than patching them. Onnsw-infra-prod, plan the rollout and re-check PVC bindings for the opendkim keys and the SMTP spool.opengovmail-config/(or leftoversilver-config/) directories on dev machines topingmailer-config/, and updateCERT_PATHin.env.