chore(ci): omit null layer metadata fields - #8416
Merged
Merged
Conversation
Placeholder layer versions can omit optional metadata such as LicenseInfo. Remove null values from the publish request so the AWS CLI accepts these versions during partition deployment. Refs #7975
|
svozza
approved these changes
Sep 1, 2026
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
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.



Issue number: closes #8417
Summary
Changes
Omit null optional metadata fields when constructing the partition layer publish request. Placeholder layer versions can omit fields such as
LicenseInfo; passing those fields as JSONnullcauses AWS CLI parameter validation to fail before deployment.User experience
Partition deployments can copy placeholder layer versions without failing on absent optional metadata. This change does not alter partition synchronization behavior.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.