mirror of
https://github.com/shankar0123/certctl.git
synced 2026-06-07 15:51:30 +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:
@@ -18,7 +18,7 @@ import (
|
||||
// inversion) so the handler stays decoupled from the concrete
|
||||
// *service.ApprovalService.
|
||||
//
|
||||
// Rank 7 of the 2026-05-03 Infisical deep-research deliverable, commit 3
|
||||
// Rank 7 of the 2026-05-03 deep-research deliverable, commit 3
|
||||
// of 4 — the API + RBAC layer.
|
||||
type ApprovalServicer interface {
|
||||
Approve(ctx context.Context, requestID, decidedBy, note string) error
|
||||
|
||||
@@ -89,8 +89,8 @@ type VaultRenewalSnapshotter interface {
|
||||
// (via NotificationService.SetExpiryAlertMetrics) and exposing
|
||||
// (here).
|
||||
//
|
||||
// Rank 4 of the 2026-05-03 Infisical deep-research deliverable
|
||||
// (cowork/infisical-deep-research-results.md Part 5).
|
||||
// Rank 4 of the 2026-05-03 deep-research deliverable
|
||||
// (cowork/deep-research-results-2026-05-03.md Part 5).
|
||||
type ExpiryAlertSnapshotter interface {
|
||||
// SnapshotExpiryAlerts returns one entry per non-zero counter,
|
||||
// pre-sorted by (channel, threshold, result) so the Prometheus
|
||||
@@ -123,7 +123,7 @@ type MetricsHandler struct {
|
||||
// certctl_vault_token_renewals_total{result=...}.
|
||||
vaultRenewals VaultRenewalSnapshotter
|
||||
// Per-policy multi-channel expiry alert counters. Rank 4 of the
|
||||
// 2026-05-03 Infisical deep-research deliverable. nil disables
|
||||
// 2026-05-03 deep-research deliverable. nil disables
|
||||
// emission of certctl_expiry_alerts_total{channel,threshold,result}.
|
||||
expiryAlerts ExpiryAlertSnapshotter
|
||||
}
|
||||
@@ -168,7 +168,7 @@ func (h *MetricsHandler) SetVaultRenewals(c VaultRenewalSnapshotter) {
|
||||
|
||||
// SetExpiryAlerts wires the per-policy multi-channel expiry-alert
|
||||
// counter table for the Prometheus exposition. nil disables the
|
||||
// block. Closes Rank 4 of the 2026-05-03 Infisical deep-research
|
||||
// block. Closes Rank 4 of the 2026-05-03 deep-research
|
||||
// deliverable.
|
||||
func (h *MetricsHandler) SetExpiryAlerts(c ExpiryAlertSnapshotter) {
|
||||
h.expiryAlerts = c
|
||||
@@ -502,7 +502,7 @@ func (h MetricsHandler) GetPrometheusMetrics(w http.ResponseWriter, r *http.Requ
|
||||
}
|
||||
|
||||
// Per-policy multi-channel expiry-alert counters. Rank 4 of the
|
||||
// 2026-05-03 Infisical deep-research deliverable. Operators alert
|
||||
// 2026-05-03 deep-research deliverable. Operators alert
|
||||
// on certctl_expiry_alerts_total{result="failure"} > 0 to catch
|
||||
// when a notifier connector (PagerDuty / Slack / etc.) is
|
||||
// rejecting our sends. Cardinality: 6 channels × N thresholds × 3
|
||||
|
||||
Reference in New Issue
Block a user