Skip to content

[Draft] API Documentation Updates for v1.181.0#1671

Draft
github-actions[bot] wants to merge 3 commits into
masterfrom
api-docs-v1.181.0
Draft

[Draft] API Documentation Updates for v1.181.0#1671
github-actions[bot] wants to merge 3 commits into
masterfrom
api-docs-v1.181.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

API Version: 1.181.0

This PR was automatically generated by the API docs workflow.

What's included

  • ✅ New base spec copied from Platform repo
  • ✅ Comparison overlay generated
  • ✅ Changes analyzed and categorized
  • ✅ Claude-generated overlay files (requires review)

Source Information

  • Platform ref: v26.2.0-cycle63_25c41d3
  • Platform commit: v26.2.0-cycle63_25c41d3
  • Triggered by: llewellyn-sl

Next steps

  1. Review Claude-generated overlays in claude-generated-overlays.md
  2. Extract overlay files from the markdown into separate YAML files
  3. Edit overlays for accuracy and completeness
  4. Run validation: python scripts/validate_overlay.py <file>
  5. Request engineering review from appropriate team
  6. Once approved, add label overlays-approved to trigger Phase 3

Analysis Summary

See analysis JSON file for detailed breakdown of changes.

- New base spec: seqera-api-1.181.0.yaml
- Comparison overlay generated
- Analysis report created
- Claude-generated overlays ready for review
@llewellyn-sl
llewellyn-sl changed the base branch from codex/isolate-api-docs-version-checkout to master July 20, 2026 17:58
@llewellyn-sl llewellyn-sl self-assigned this Jul 20, 2026

@tcrespog tcrespog left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed audit logs content: looks good to me overall.

Unrelated question regarding these "overlays": couldn't the edits present in the overlays be applied at the source Platform OpenAPI model/definition directly? Ideally, handling a single source of truth would make it easier to maintain (say, we introduce a new actor type for audit logs).

At least for API v2, now that it is going to start being implemented, perhaps we want to minimize our reliance on overlays.

@@ -0,0 +1,1614 @@
I'll generate the OpenAPI overlay files for version 1.181.0, organized by controller/tag. I'll create operations, parameters, and schemas overlays for each affected area.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this statement is not meant to be part of the document.

update: "Filter logs with timestamp on or before this date in ISO 8601 format."

- target: "$.paths['/admin/audit-logs-v2/{auditLogId}'].get.parameters[?(@.name=='attributes')].description"
update: "Additional attribute values to include in the response. Accepts `state` for pre/post change images. Returns an empty value if omitted."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Returns an empty value if omitted

If omitted, the state images content is not present.

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