Added projection level option to clusters update command

[aneshas]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add projection level option to clusters update command

✨ Enhancement

Walkthroughs

Description

• Add projection level option to cluster update command
• Support off, system, or user projection levels
• Extend UpdateClusterRequest with projection_level field

Diagram

flowchart LR
  CLI["CLI UpdateCluster struct"]
  PARSE["Parse projection_level argument"]
  API["UpdateClusterRequest struct"]
  CALL["API call with projection_level"]
  CLI -- "add projection_level field" --> PARSE
  PARSE -- "pass to request" --> API
  API -- "send to endpoint" --> CALL

Loading

File Changes

1. cli/src/main.rs ✨ Enhancement +8/-0

Add projection level CLI option to update command

• Add projection_level field to UpdateCluster struct with custom parser
• Field accepts off, system, or user projection levels
• Pass projection_level parameter to UpdateClusterRequest in API call

cli/src/main.rs

---

2. generated/src/mesdb/schemas.rs ✨ Enhancement +2/-0

Add projection level field to request schema

• Add projection_level field to UpdateClusterRequest struct
• Field is optional and skipped during serialization if None
• Supports ProjectionLevel enum type

generated/src/mesdb/schemas.rs

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Public API struct break 🐞 Bug ⚙ Maintainability

Description

generated::mesdb::UpdateClusterRequest gained a new public field, which causes compile errors for
any downstream crate constructing it with a struct literal (they must now add `projection_level:
...`). This is a breaking change to the generated client API surface and should be handled via
versioning and/or safer construction patterns.

Code

generated/src/mesdb/schemas.rs[R586-587]

+    #[serde(skip_serializing_if = "Option::is_none")]
+    pub projection_level: Option<ProjectionLevel>,

Evidence

UpdateClusterRequest is a pub struct, so adding a field changes its construction requirements
for all consumers; the CLI had to be updated in this PR to include the new field in the struct
literal, demonstrating the impact. While the new field is optional for serialization, it is still
mandatory to mention in Rust struct literals unless using a helper like Default + struct update
syntax.

generated/src/mesdb/schemas.rs[577-588]
cli/src/main.rs[2941-2953]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`UpdateClusterRequest` is a public struct and a new field was added (`projection_level`). This is a breaking change for downstream Rust code that constructs `UpdateClusterRequest` using a struct literal, because Rust requires all fields to be present unless using struct update syntax.

### Issue Context
Within this repo, `cli/src/main.rs` was updated to include the new field, but external consumers of the generated client types may still break at compile time.

### Fix Focus Areas
- generated/src/mesdb/schemas.rs[577-588]

### Suggested fix
- Add `Default` support for `UpdateClusterRequest` (e.g., `#[derive(Default)]` or an explicit `impl Default`) so consumers can write `UpdateClusterRequest { acl_id: ..., ..Default::default() }` and be resilient to future optional-field additions.
- If these crates are published, ensure the change is reflected in semver/versioning notes (breaking-change acknowledgment).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[linear]

CLO-260 Update `esc` to support `RunProjections` change