You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
According to the ecctl documentation example, using the --kind flag with --generate-update-payload should generate an update payload specific to the chosen resource (e.g., elasticsearch, kibana, apm, etc.).
However, the following commands produce the same payload output for both Elasticsearch and Kibana:
Expected Behavior:
Each --kind should scope the payload to the corresponding resource only:
--kind elasticsearch → only Elasticsearch plan/settings
--kind kibana → only Kibana plan/settings
Actual Behavior:
The resulting JSON files (elasticsearch.json and kibana.json) are identical, which contradicts the expected behavior described in the documentation.
Impact:
This makes it impossible to generate accurate update payloads for individual resources, blocking granular updates or validation workflows in automation pipelines.