Skip to content

SDKQE-3978: add an option to enable the Capella Data API at cluster create time - #18

Open
emilienbev wants to merge 1 commit into
mainfrom
SDKQE-3978
Open

SDKQE-3978: add an option to enable the Capella Data API at cluster create time#18
emilienbev wants to merge 1 commit into
mainfrom
SDKQE-3978

Conversation

@emilienbev

Copy link
Copy Markdown
Contributor

cbdinocluster can enable the Capella Data API during cluster creation with cloud.data-api: true. Enabling it on a running cluster takes several minutes, so a test that needs the Data API should request it at allocate time. It also adds those minutes to the allocation, so it must be off by default.

  • Add capellaDataApi (boolean, optional, default off) to the cluster definition config. When true, the generated cloud section contains data-api: true.
  • Emit the field on the Capella Server path only. Columnar clusters reject it.
  • Add a confirm prompt in the Capella flow of the definition creator, default no.
  • When the option is off, the generated definitions are byte-identical to main.

Verified with bun run typecheck and bun run test (895 pass, includes three new tests). Lint findings are identical to main. Not verified against live Capella.

…reate time

- Add capellaDataApi to ClusterDef. When true, the generated cloud
  section gets data-api: true for Capella Server clusters only.
- Off by default: the Data API adds minutes to each allocation, and
  Capella Analytics rejects the field.
- The definition builder asks for it in the Capella flow and reads it
  back from existing cluster configs.
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