Skip to content

Conversation

andrewkroh
Copy link
Member

Previously, elastic-package would send null values for variables without defaults, causing Fleet API validation errors for non-required URL-type variables. This change modifies the variable handling to skip unset variables that have no default values instead of including them as nulls.

Fixes #2979

Previously, elastic-package would send null values for variables without
defaults, causing Fleet API validation errors for non-required URL-type
variables. This change modifies the variable handling to skip unset
variables that have no default values instead of including them as
nulls.

Fixes elastic#2979
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

@andrewkroh andrewkroh marked this pull request as ready for review October 8, 2025 16:05
@jsoriano
Copy link
Member

jsoriano commented Oct 9, 2025

test integrations

Copy link
Member

@jsoriano jsoriano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! Let's wait to test with integrations repository.

@elastic-vault-github-plugin-prod

Created or updated PR in integrations repository to test this version. Check elastic/integrations#15618

@andrewkroh
Copy link
Member Author

The testing has completed. See my notes at elastic/integrations#15618 (comment).

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.

Null package policy variables cause API validation errors in Fleet
3 participants