[APIM 4.5.0] Add ApiPolicies field to APIDTODefinition and integration API struct#1357
Merged
Merged
Conversation
This was referenced Jun 17, 2026
npamudika
approved these changes
Jun 17, 2026
RakhithaRR
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
apictl init --definition silently drops API-level apiPolicies when unmarshalling the definition YAML into APIDTODefinition.
Root cause
The struct was missing the ApiPolicies field. YAML/JSON decoders discard unknown keys.
Fix
Added ApiPolicies interface{} to APIDTODefinition in specs/v2/apispec.go
Added same field to integration test helper API struct in integration/apim/apiDTO.go
Impact
API-level policies now round-trip correctly through apictl init --definition → import → Publisher API.