From e031cc10d6b0db3c3114a63833e6e864e185eaec Mon Sep 17 00:00:00 2001 From: Sean Keever <33592180+swkeever@users.noreply.github.com> Date: Fri, 13 Nov 2026 13:14:19 -0500 Subject: [PATCH] docs(platform): port the git migrations and LavaFlow intake docs from volcano-hosting Ports the docs/public changes in Kong/volcano-hosting#3406 and #3412. --- content/platform/guides/lavaflow.md | 9 ++++++--- content/platform/projects/git-deploy.md | 11 ++++++++++- 2 files changed, 16 insertions(+), 4 deletions(-) diff --git a/content/platform/guides/lavaflow.md b/content/platform/guides/lavaflow.md index 5e5ddc9..05db065 100644 --- a/content/platform/guides/lavaflow.md +++ b/content/platform/guides/lavaflow.md @@ -1753,8 +1753,9 @@ of your project's exact secret values, or a secret that [gitleaks](https://github.com/gitleaks/gitleaks)' default rules detect, reads `Hidden: this field matched a secret.` in place of its whole text. Nothing else is hidden, so text that only looks like a credential, such as a test's -fixture, stays readable. A path that holds a secret reads `""`, and so does a -log line's `level`. On a run held with `possible_credential`, the fix's +fixture, stays readable. A path that holds a secret or a control character +reads `""`, and so does a log line's `level`; a hold reason with such a path +hides its question too. On a run held with `possible_credential`, the fix's summary, review text, statements, check commands and output, and hold reasons read `Hidden: the fix may add a credential.` @@ -1923,7 +1924,9 @@ Findings, questions, observations and statements are the reviewers' and the fix's own words, and can quote your code. Each is shown whole, or reads `Hidden: this field matched a secret.` when it holds a secret, as [a run's other text](#follow-runs) does. A finding whose `file` -holds a secret reads `""` there. +holds a secret or a control character reads `""` there, and its +`explanation` reads `Hidden: this field matched a secret.`, since it may +quote that path. A secret value is the value of one of your project's secret variables, such as an `API_KEY`, or a password in a URL variable; either counts at 8 characters or diff --git a/content/platform/projects/git-deploy.md b/content/platform/projects/git-deploy.md index 16736a5..7f3134d 100644 --- a/content/platform/projects/git-deploy.md +++ b/content/platform/projects/git-deploy.md @@ -753,7 +753,16 @@ Before you turn it on, and require pull request reviews, so every migration is reviewed before it reaches that branch. -The settings `PUT` is a full replace, except `apply_migrations`. In platform +From the CLI, turn it on with: + +```bash +volcano git migrations on +``` + +It asks you to confirm; `--yes` skips the prompt, for CI and agents. +`volcano git migrations off` turns it off, and `volcano git status` shows it. + +Over the API, the settings `PUT` is a full replace, except `apply_migrations`. In platform mode, omitting `frontend_name` clears it. In Git mode, stopping the selected legacy frontend requires an explicit `"frontend_name": ""`; omission is refused. Read the saved settings first: