vladislav-kuryata opened a new issue, #10615: URL: https://github.com/apache/gravitino/issues/10615
### What would you like to be improved? ### Summary Please add a `dry-run` mode to Gravitino API operations that create/update/delete metadata objects and governance bindings. ### Problem Today, metadata changes are applied directly, which makes it hard to safely validate impact before execution. For GitOps workflows, teams need a way to preview changes (plan) before apply. ### Proposal Introduce a dry-run capability (for example via query param/header/flag) that: - validates request payloads and permissions, - resolves target objects and dependencies, - computes the expected diff, - returns what would change, - does **not** persist any changes. ### Expected response (example) For dry-run requests, return structured output such as: - operation type (`create`, `update`, `delete`), - target object(s), - before/after snapshot or field-level diff, - validation results and warnings, - dependency/conflict information, - final status: `would_apply=true/false`. ### Why this is important - safer production operations, - better CI/CD and GitOps integration (`plan -> review -> apply`), - easier change review and approvals, - simpler rollback planning and auditability. ### Suggested scope Dry-run support for at least: - catalogs/schemas/tables/models/topics/filesets, - tags and policy associations, - permission/governance-related updates. ### Acceptance criteria - [ ] API supports dry-run mode for key mutating endpoints. - [ ] Dry-run never modifies server state. - [ ] Response includes machine-readable diff/details. - [ ] Validation and authorization are executed in dry-run. - [ ] Documentation includes examples and behavior guarantees. ### How should we improve? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
