When packages are upgraded, they don't stomp on existing configurations, however with the switch to YAML config, the packager doesn't think there's a configuration and installs a new one. This has no api_key set, so the agent will start, see that there is a "good" agent.yml, load it, and fail with no api_key (or indeed, no customized configuration of any kind).
So, the package should have a check for the TOML version in the absence of the YAML version, and simply not install the default YAML file if one of those exists.
When packages are upgraded, they don't stomp on existing configurations, however with the switch to YAML config, the packager doesn't think there's a configuration and installs a new one. This has no
api_keyset, so the agent will start, see that there is a "good"agent.yml, load it, and fail with noapi_key(or indeed, no customized configuration of any kind).So, the package should have a check for the TOML version in the absence of the YAML version, and simply not install the default YAML file if one of those exists.
This BLOCKS release.