Repository navigation
Conversation
…s backend Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015pcV34KcZ9UzUQGmj35oJJ
…igger-asset endpoint Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rigger-asset Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…events' into DCV-4184-security-docs-6.2
…flow API token scope Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 18, 2026
…o status, and when the fingerprint appears Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s under Extra Fields Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This reverts commit 52299de. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Summary
One PR for the 6.2 security and Airflow API documentation, replacing #77 and #80 so it can be reviewed and merged together (DCV-4184 is the end-to-end check of these changes).
From #77 (DCV-4077): new how-to page for credentials whose value lives in the customer's own secrets backend (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault) and is rotated there without touching Datacoves:
It covers requirements, supported backends, storing and referencing the secret, rotation (with the
RSA_PUBLIC_KEY_2overlap for Snowflake), status badges, notifications and troubleshooting. The Snowflake key-pair, service connections and projects pages link to it.From #80 (DCV-4143): Datacoves API keys for the Airflow API (Airflow 2 and 3, sent as a
Bearertoken) and thetrigger-assetendpoint, with curl and Python examples, the Environment Keys screenshot, and the dag-parse-times page adjusted to the new keys.New here:
DATACOVES__API_TOKENas a low-privilege per-environment token and says the tasks no longer get the admin service account's credentials, pointing to API keys for calling the Airflow API.Not included: the Airflow 3 Azure Data Factory page, which applies to every release and went out on its own in #84; the 6.1 pages for the secrets backend selection (#61) and Snowflake authentication (#79), which ship with 6.1. A link from the Snowflake section here to the Snowflake sign-in page of #79 can be added once it merges.
npm run buildpasses; its only broken-anchor warning (dag-parse-times->datacoves-my-parse-logs) is also onmain.Merge once 6.2 is released.
Checklist
🤖 Generated with Claude Code