Skip to content

Correct Registry ingestion guidance and document tested installation options - #2

Open
ndbroadbent wants to merge 1 commit into
mainfrom
docs/registry-ingestion-guidance
Open

ndbroadbent wants to merge 1 commit into
mainfrom
docs/registry-ingestion-guidance

Conversation

@ndbroadbent

Copy link
Copy Markdown
Member

The release instructions incorrectly treated a missing repository webhook as a fault and recommended Resync without checking its deletion preview. Claimed namespaces receive GitHub App events, and the reported preview would remove existing releases.

Document the already-registered signing key, the claimed-namespace settings, and the ingestion failure tracked in HashiCorp issue #67. Describe two verified installation paths: pinning 0.1.12 for the unchanged mailer example, or installing the signed 0.2.2 release through a filesystem mirror.

Validation (2026-10-21, Terraform 1.13.4, macOS ARM64):

  • Normal Registry installation of 0.1.12 passed terraform init, generated the expected mailer/delivered filter, and rejected the deliberate deliverd typo.
  • The published 0.2.2 archive passed checksum verification against its GPG-verified SHA256SUMS. Mirror installation passed the same init and valid/invalid plan checks.
  • Compared the 0.1.12 and 0.2.2 catalogs: mailer events are unchanged; other integrations have changes, which the guidance explicitly limits.
  • git diff --check passed. No apply or Registry account changes were made.

@ndbroadbent ndbroadbent added documentation Improvements or additions to documentation priority: high High priority review: standard Standard review labels Oct 21, 2026
@ndbroadbent

Copy link
Copy Markdown
Member Author

QA — 2026-10-21, commit b00c156e255d2391dd597b83b2205d5ea3d50b6c:

  • Provider CI passed build, vet and tests: https://github.com/DocSpring/terraform-provider-logstruct/actions/runs/39545537212
  • Terraform 1.13.4 on macOS ARM64 installed 0.1.12 from the Registry and 0.2.2 through an isolated filesystem mirror. Both produced { $.evt = "delivered" && $.src = "mailer" } for the valid example and rejected deliverd with the expected invalid-event diagnostic.
  • The 0.2.2 archive checksum matched the GPG-verified release manifest. The signature uses the already-registered key BD2DE4CA3CF5BA4D.
  • Compared the release catalogs: mailer events are identical; other integrations have changes, as documented.
  • git diff --check passed. No Terraform apply, key rotation, App permission change, namespace change, or Resync was performed. Normal Registry installation of 0.2.2 remains unavailable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation priority: high High priority review: standard Standard review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant