mirror of
https://github.com/shankar0123/certctl.git
synced 2026-06-13 22:28:52 +00:00
chore: drop 'Infisical' label from internal references
Strategic naming cleanup. Earlier doc-comments + commit messages framed Rank 4 / Rank 5 / Rank 7 work as 'Rank N of the 2026-05-03 Infisical deep-research deliverable' — the 'Infisical' qualifier was a holdover from the original deep-research framing where Infisical (a competing secrets-management platform) was the comparator. Keeping the comparator's name in our source adds noise without value; an external reader sees 'Infisical' and assumes a dependency or shared lineage rather than reading it as the competitive context it was. Mechanical sed across 34 files (32 source / docs + 2 follow-up Python passes to collapse 'deep-research deep-research' duplicates that emerged where the original phrase wrapped across lines): s|Infisical deep-research|deep-research|g s|infisical-deep-research-results|deep-research-results-2026-05-03|g s|infisical-deep-research-prompt|deep-research-prompt-2026-05-03|g s|infisical-deep-research|deep-research|g s|Infisical|deep-research|g s|deep-research deep-research|deep-research|g # collapse-pass Net diff: 63 insertions / 64 deletions across cmd/, docs/, internal/, migrations/. Pure text substitution; zero behavior change. Code path unchanged — go vet clean, tests for TestApproval pass on both internal/service and internal/api/handler packages. Workspace docs (cowork/) carry the same references and will be swept separately — they're not under certctl/ git control. The two filename references (cowork/infisical-deep-research-results.md + cowork/infisical-deep-research-prompt.md) get renamed alongside that sweep to deep-research-results-2026-05-03.md / deep-research-prompt-2026-05-03.md so cross-references in the certctl repo doc-comments resolve cleanly.
This commit is contained in:
@@ -54,7 +54,7 @@ type NotificationService struct {
|
||||
// to SendThresholdAlertOnChannel reports its outcome (success / failure)
|
||||
// to the metric sink so the Prometheus exposer surfaces
|
||||
// certctl_expiry_alerts_total{channel,threshold,result}. Rank 4 of the
|
||||
// 2026-05-03 Infisical deep-research deliverable. Nil leaves the
|
||||
// 2026-05-03 deep-research deliverable. Nil leaves the
|
||||
// dispatch path unchanged (no metric emission, but alerts still fire).
|
||||
expiryAlertMetrics ExpiryAlertRecorder
|
||||
}
|
||||
@@ -149,7 +149,7 @@ func (s *NotificationService) SendExpirationWarning(ctx context.Context, cert *d
|
||||
//
|
||||
// Policy-driven dispatch in RenewalService.sendThresholdAlerts uses
|
||||
// SendThresholdAlertOnChannel directly with the channel resolved from the
|
||||
// per-policy AlertChannels matrix. Rank 4 of the 2026-05-03 Infisical
|
||||
// per-policy AlertChannels matrix. Rank 4 of the 2026-05-03 deep-research
|
||||
// deep-research deliverable.
|
||||
func (s *NotificationService) SendThresholdAlert(ctx context.Context, cert *domain.ManagedCertificate, daysUntilExpiry int, threshold int) error {
|
||||
return s.SendThresholdAlertOnChannel(ctx, cert, daysUntilExpiry, threshold, domain.NotificationChannelEmail)
|
||||
|
||||
Reference in New Issue
Block a user