Skip to content

search.SearchService: support new resource fields via latest API version 2026-04-01 #5378

Description

@BogdanRusuUiPath

Describe the current behavior

search.SearchService does not expose properties.encryptionWithCmk on the spec. The underlying ARM resource Microsoft.Search/searchServices supports a service-level setting encryptionWithCmk.enforcement (values: Enabled / Disabled / Unspecified) that, when Enabled, enforces that every child object (indexes, indexers, data sources, skillsets, synonym maps) carries its own encryptionKey. Without ASO exposing this, operators have no declarative way to require CMK at the service boundary — the only path today is direct ARM PATCH or az search service update, which then drifts every reconcile.

Describe the improvement

Add an optional encryptionWithCmk field to SearchServiceSpec mirroring the ARM shape:

apiVersion: search.azure.com/v1api20231101
kind: SearchService
metadata:
  name: my-search
spec:
  encryptionWithCmk:
    enforcement: Enabled
  # ... existing fields ...

Optional and backward compatible — existing manifests without encryptionWithCmk keep behaving as today. The Go SDK (armsearch.Service.Properties.EncryptionWithCmk) already has full coverage, so the generator should pick it up cleanly.

Additional context

Metadata

Metadata

Assignees

Labels

good-for-copilot 🤖An issue that is a good candidate for implementation by AInew-resource-versionNew version of a resource ASO already supports

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions