I recently updated to 0.29.0, and when running profiles list I encounter this error:

$ elastic-package profiles list
Error: error listing all profiles: error loading profile 7.12.0: error reading in profile 7.12.0: error reading in profile: reading filed failed (path: /.../.elastic-package/profiles/7.12.0/stack/elasticsearch.config.default.yml): open /.../.elastic-package/profiles/7.12.0/stack/elasticsearch.config.default.yml: no such file or directory

I think this is a side effect of all the changes happening around profiles and configurations to support 8.0, but this is quite a pain. I have some old profiles with custom configuration for testing some specific use cases that require manual updating. While not expecting backward compatibility, this kind of issue create effort downstream and make relying on this tool more risky.

To me this highlights that profiles are quite fragile today. I have some improvements idea that gathers around simplifying the current profile structure, also given that after the introduction of --version flag for stack commands is possible to combine profiles and versions (making this troublesome to manage and debug).

Are there any proposals to improve the current profiles to make them more future proof? (I've seen #557 but seems more code centric than user centric).