Would you consider supporting `machine` executors in `circleci local execute`?

[kienstra]

What problem does this feature solve?:

Using circleci local execute for many more jobs, and often the most useful jobs to debug, like e2e tests.

This CircleCI CLI is amazing, it sets CircleCI apart.

circleci local execute doesn't support machine executors, only Docker executors.

That's understandable, as they 'require an extra VM to run their jobs.' But machine support would help a lot.

Provide an example:

Some of the most useful jobs to debug with the CLI are e2e tests.

Those more likely to fail only in CI, and not in your local environment.

And often, e2e tests run on machine executors. Maybe because they can come with a lot installed, like Docker.

Examples:

• hashicorp/vault-csi-provider
• GoogleCloudPlatform/django-cloud-deploy
• InfuseAI/primehub
• observatorium/operator
• More

GitHub shows 37,006 .circleci/config.yml files that have machine, thought many times machine doesn't refer to the executor.

If you're open to considering it, supporting machine executors could add a lot of power to an already industry-leading CLI.

Thanks!

[abdelDriowya]

Hi @kienstra, thanks for your suggestion. 
I will check internally with the team, and get back to you asap

[kienstra]

Hi @abdelDriowya, thanks so much for asking about this!