Skip to content

SOD-824: Add scalingOrientation (orientation) field to Ocean AKS VNG strategy - #852

Merged
anjanobalesh merged 1 commit into
masterfrom
SOD-824
Aug 20, 2026
Merged

SOD-824: Add scalingOrientation (orientation) field to Ocean AKS VNG strategy#852
anjanobalesh merged 1 commit into
masterfrom
SOD-824

Conversation

@anjanobalesh

Copy link
Copy Markdown
Collaborator

Jira: https://flexera.atlassian.net/browse/SOD-824

What

Adds the orientation field to the shared ocean-strategy.yaml schema under api/services/ocean/aks/schemas/, used by the strategy object across all 4 Ocean AKS VNG operations (they all $ref the same schema file):

  • Create VNG (oceanAKSVirtualNodeGroupCreate)
  • Get/List VNG (oceanAKSVirtualNodeGroupGet / oceanAKSVirtualNodeGroupList)
  • Update VNG (oceanAKSVirtualNodeGroupUpdate)
  • Import VNG (oceanAKSVirtualNodeGroupImport)

Field

  • Name: orientation (kept as-is to match the actual field name implemented in spotinst-api / spotinst-azure-ocean-common — the story named it scalingOrientation, but no rename was made in code, so the doc uses the real field name to stay accurate)
  • Type: string, enum [cost, availability]
  • Default: cost
  • Description: "Set this value to control and manage optimization priorities."

Verification

  • yarn validate (swagger-cli validate) — pass
  • yarn bundle:swagger — pass
  • npx @redocly/cli lint — no new errors/warnings introduced (3 pre-existing errors unrelated to this file)
  • yarn bundle:redoc fails on this branch and equally on master (pre-existing redoc-cli React "Invalid hook call" dependency conflict, unrelated to this change)

Acceptance criteria

  • orientation appears under strategy for all 4 ops (shared schema)
  • Both values (cost, availability) documented via enum
  • Default cost stated
  • Samples auto-generated from schema example: cost

@anjanobalesh
anjanobalesh requested a review from a team as a code owner August 20, 2026 09:36
@anjanobalesh
anjanobalesh merged commit 553e5ff into master Aug 20, 2026
5 checks passed
@anjanobalesh
anjanobalesh deleted the SOD-824 branch August 20, 2026 12:29
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