Skip to content

--generate-update-payload --kind returns identical payloads for different resource types (elasticsearch, kibana) #723

@TomonoriSoejima

Description

@TomonoriSoejima

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:

Steps to Reproduce:

ecctl deployment show f8c26c744a09459586bfd141e3d2fd6c --generate-update-payload --kind elasticsearch > elasticsearch.json
ecctl deployment show f8c26c744a09459586bfd141e3d2fd6c --generate-update-payload --kind kibana > kibana.json
diff elasticsearch.json kibana.json

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.

Related Documentation:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions