Skip to content

fix(ngts): refresh NGTS spec (path cleanup + fingerprint field clarification) - #1468

Merged
rajitshah-ca merged 2 commits into
PaloAltoNetworks:masterfrom
rajitshah-ca:fix/ngts-spec-refresh-2026-09-10
Sep 15, 2026
Merged

rajitshah-ca merged 2 commits into
PaloAltoNetworks:masterfrom
rajitshah-ca:fix/ngts-spec-refresh-2026-09-10

Conversation

@rajitshah-ca

@rajitshah-ca rajitshah-ca commented Sep 10, 2026 •

Copy link
Copy Markdown
Contributor

What

Refreshes the NGTS (Venafi TLS Protect Cloud) OpenAPI spec on pan.dev from the latest ua-repo pan.dev pipeline runs:

Changes

  • Certificate endpoint paths: dropped the /outagedetection prefix (e.g. /outagedetection/v1/certificates -> /v1/certificates). This matches the same path change already deployed to developer.venafi.com by the same pipeline run's Dev Central job (Deploy API Production), so this brings pan.dev in line with what's already live on the primary docs.
  • "Built-in Accounts" tag casing: corrected from Built-In Accounts to Built-in Accounts, matching ua-repo's source of truth (siteconf-pandev.yaml), which was corrected there shortly after the capitalized version was originally published to this repo and never republished.
  • existingCertificateFingerprint field description clarified: CertificateRequestRequest.existingCertificateFingerprint now specifies it's a SHA-1 fingerprint (was previously just "Fingerprint of an existing inventory certificate...").
  • New containerFormat query param on GET /v1/certificates/{id}/contents, and a new POST /v1/machines/workflows endpoint (machines_initiateTestConnectionWorkflow), carried over from the regenerated spec.

No Docusaurus config, sidebar, or generated page changes needed — generated files aren't committed (built at deploy time), consistent with #1311.

Motivation and Context

EPIC: VC-50859

How Has This Been Tested

  • Verified path/naming changes against ua-repo source (siteconf-pandev.yaml, operationsDoc/) and confirmed the path change is already live on developer.venafi.com via the same pipeline run.
  • Diffed schema-level field descriptions between pipeline runs to confirm the existingCertificateFingerprint wording change and rule out unrelated component $ref renumbering noise.
  • Validated the spec is well-formed JSON.

🤖 Generated with Claude Code

Regenerates the TLS Protect Cloud OpenAPI spec from the latest ua-repo
pan.dev pipeline run to pick up two changes already live upstream:

- Certificate endpoint paths dropped the /outagedetection prefix
  (e.g. /outagedetection/v1/certificates -> /v1/certificates), matching
  the same change already deployed to developer.venafi.com by the same
  pipeline run.
- "Built-in Accounts" tag casing corrected to match ua-repo's source of
  truth (siteconf-pandev.yaml), which was fixed after the original
  capitalized version was published here.

EPIC: VC-50859

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 11, 2026 •

Copy link
Copy Markdown

Visit the preview URL for this PR (updated for commit a9a6c89):

https://pan-dev-f1b58--pr1468-sztqzd6d.web.app

(expires Tue, 22 Sep 2026 07:00:05 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 9359a9fa100d5fdb082f75280473a90b1f96eb51

Regenerates the NGTS spec from ua-repo pipeline 2848060423 to pick up
one content change: CertificateRequestRequest.existingCertificateFingerprint's
description now specifies it's a SHA-1 fingerprint.

EPIC: VC-50859

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@rajitshah-ca rajitshah-ca changed the title fix(ngts): refresh NGTS spec from ua-repo pipeline fix(ngts): refresh NGTS spec (path cleanup + fingerprint field clarification) Sep 14, 2026
@rajitshah-ca
rajitshah-ca merged commit f035365 into PaloAltoNetworks:master Sep 15, 2026
6 checks passed

This branch was successfully deployed

2 active deployments
preview — a9a6c89e Deployed Sep 15, 2026 by rajitshah-ca via Delete preview channel #243
default — a9a6c89e Deployed Sep 14, 2026 by rajitshah-ca via Analyze Unsafe (javascript) #3575
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants