Wrong error message: "nothing to run"

[Nuru]

• Checkout atmos v0.5.0
• cd example/

$ VARIANT_DIR=cli variant run helmfile lint nginx-ingress -s ue2-dev
nothing to runError: nothing to run

This appears to be due to subjob "aws eks kubeconfig" error

Error: .variant2/cache/https_git@github_com_cloudposse_atmos.ref=master/modules/kubeconfig/kubeconfig.variant:40,42-73: Unsupported attribute; This object does not have an attribute named "kubeconfig_profile_environment".

Ideally we should see an error message with some kind of stack trace (doesn't have to include line numbers) like

"aws eks kubeconfig": Error:  Unsupported attribute; This object does not have an attribute named "kubeconfig_profile_environment"
"helmfile subcommand"
"helmfile lint"

[mumoshu]

@Nuru Thanks for reporting! Pleaser see #40 - After that we get more descriptive errors like the below:

$ VARIANT_DIR=cli variant run helmfile lint nginx-ingress -s ue2-dev
config "helmfile-command": source 0: job "helmfile-command": job "helmfile-command" is not definedError: job "helmfile subcommand": config "helmfile-command": source 0: job "helmfile-command": job "helmfile-command" is not defined

In this specific case, it seems that the root cause is that job "helmfile-command" is not defined - the helmfile-command job is not defined in any of atomis modules.

[mumoshu]

@Nuru v0.36.0 has been released with #40

[Nuru]

@Nuru v0.36.0 has been released with #40

I do not mean to sound ungrateful, but have you fixed #36 yet, or am I still forced to update everywhere now?