Improved logic of k3ai init

[alexarnoldy]

I'm still starting out with K3AI but I think the logic of the init subcommand could use some improvement.

It seems like if you run k3ai init when there is no config.yaml file, it creates the file and nothing else.

If you run the command after there is a config.yaml file, it applies the configuration described in the file.

If that's correct, it seems a little unusual to me. Have you thought of maybe rolling the cluster creation into the apply subcommand?

Perhaps in that way you could use the invocation of init to create the file if it doesn't exist, plus it could summarize what the resulting cluster config would be in all cases. That would lend itself to more consistent behaviour of init.

[k3aibot]

I've opened an Issue What will happen now?

So here it is what our super duper bot will do for you 👇

1. Our Super Duper @k3aibot will add some label to your issue to your issue to better track it
2. Second @k3aibot will move the issue into our funnel here (General Funnel Board)[https://github.com/orgs/kf5i/projects/3]
3. One of the K3ai members will be assigned to review your issue and start the real job on it
   Oh one last thing if you like to speed up the entire process let us know what kind of issue is this adding one of these labels (only one per comment)
   👇 👇 👇

• /ena this is needed if your issue require a new feature
• /bug in case you forgot to use the bug template we will take care of it
• /question if it is a Question for us
• /docs if this require us to update/refresh our docs

[k3aibot]

👍 Seems like this is the first time issue for you.

Thank You for taking the time to contribute to K3ai project!