Helidon init does not produce app.yaml for 3.x.x

[DavideRossi]

It used to work (and it's also described in the quickstart).
For some reason now it only works when selecting version 4.0.0.
Creating a project with the Maven archetype does not work either (which I guess is what helidon init does under the hood) but I admit I did not try that in the past.

[tvallin]

Indeed, this issue was reported and fixed under the Helidon repository: #7215

[DavideRossi]

I see. Still does not work with the current version of helidon init when selecting a 3.x.x version. Is there a way to fix this behavior?

[tvallin]

Yes, it will be included in the next 3.x Helidon release. Version 3.2.2 does not contain the fix

[DavideRossi]

Yet there is something weird to my eyes.
Creating a 3.x.x project results in a missing app.yaml while creating a 4.0.0 project with very same version of the helidon cli does not. This seems to suggest that the helidon cli is using different revisions of archetypes/helidon/src/main/archetype/common/presets.xml depending on the chosen Helidon version.
And, if that is the case, why it "sees" a different preset.xml for 3.x.x than what it used to "see" a couple of versions ago (given that it used to create the app.yaml file)?

[romain-grecourt]

And, if that is the case, why it "sees" a different preset.xml for 3.x.x than what it used to "see" a couple of versions ago (given that it used to create the app.yaml file)?

Archetypes are released as part of the Maven release, the change was made in #4887 which was part of 3.0.2.

Before 3.0.2 app.yaml was (incorrectly) included by default. #4887 fixed the archetype to (among other things) honor the k8s input. The preset value wasn't changed to true which is why the app.yaml file is not included in >= 3.0.2.

The fix (#7216) will be included in the next release (3.2.3). I will close this issue once 3.2.3 is available.

[m0mus]

Closing as fixed in 3.2.3