Skip to content

fleetctl get fleets returns setup_experience: null for apps #44970

Description

@spalmesano0

Fleet versions

  • Discovered: 4.84.2
  • Reproduced: 4.85.0 (Dogfood)

Web browser and operating system: N/A


💥 Actual behavior

fleetctl get fleets --yaml outputs setup_experience: null for apps instead of the correct value (setup_experience: true). This causes fleetctl apply to clear the settings when run with the output from fleetctl get.

🛠️ Expected behavior

fleetctl get fleets --yaml should preserve the correct setup_experience value (e.g. true) for apps.

🧑‍💻 Steps to reproduce

These steps:

  • Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
  • Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.
  1. Configure a fleet with apps selected for Setup experience.
  2. Export the config with fleetctl get fleets --yaml.
    • The exported YAML contains setup_experience: null instead of setup_experience: true for apps.

🕯️ More info (optional)

  • pingali used --remove-deprecated-keys, but I reproduced this with and without that.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

#g-orchestrationOrchestration product groupP2Urgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needbugSomething isn't working as documentedcustomer-pingali~assisting qaThis issue can be QA'd by anyone outside the QA team when capacity allows~fleetctlRelated to the Fleet command line tool (CLI)

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions