Skip to content

docs: describe masked secrets in integration settings - #104

Merged
ysyneu merged 1 commit into
mainfrom
sync/integration-secret-masking
Oct 16, 2026
Merged

ysyneu merged 1 commit into
mainfrom
sync/integration-secret-masking

Conversation

@ysyneu

@ysyneu ysyneu commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

What

Syncs the integration description changes from flashduty-docs into the vendored spec and regenerates models_gen.go. Comment-only change; no types or fields change.

  • IntegrationDetail.Settings / list item Settings: each saved secret is returned as ******; unset values stay empty.
  • Update Settings: a stored secret is kept only while its destination is unchanged.

Why not make sync-spec

main vendors spec additions (Automation run_in, AutomationExecutionLocation) that are not on flashduty-docs main yet. A full make sync-spec would remove them. This PR applies only the integration description lines, so the rest of openapi/ is unchanged.

Tests

make fmt (no changes), make test (race) and go build ./... pass.

Sync the integration descriptions from flashduty-docs: list, detail and
update responses return each saved secret in settings as ******, and an
update keeps a stored secret only while its destination is unchanged.

Only the integration description changes are applied to the vendored
spec; the rest of openapi/ is left as is.
@ysyneu
ysyneu merged commit ed5c0fb into main Oct 16, 2026
4 checks passed
@ysyneu
ysyneu deleted the sync/integration-secret-masking branch October 16, 2026 20:19
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.

1 participant