Alejandro Esquivel

Duplicate Issue for executor template https://github.com/AgnostiqHQ/covalent-executor-template/issues/11

Thanks for reaching out @gcamach0 ! I have assigned this issue to you. Let me know if you have any questions and I will do my best to answer :)

from @cjao: `covalent tries to assign dask as the default executor` and `dask info isn't automatically cleared from the config` so `covalent purge && covalent start --no-cluster` seems to be...

Closed by https://github.com/AgnostiqHQ/covalent/pull/1020

Ah gotcha, thanks @cjao

Please [add your planning poker estimate](https://app.zenhub.com/workspaces/Covalent-Open-Source-61a12f9cbea1d7000f1b919b/issues/AgnostiqHQ/covalent/1009?planning-poker) with ZenHub @kessler-frost

@cjao's comments: In `_format_exec_script()` (https://github.com/AgnostiqHQ/covalent-fargate-plugin/blob/1751ac1dc1dd3ef3856e4de5f74075b9bd689140/covalent_fargate_plugin/fargate.py#L282), there is a string representation of the args and kwargs passed to the function which can't possibly work for non-json type inputs

@wjcunningham7 Currently implementing a prelim schema for this should have no effect on the product as there doesn't seem to be a plan yet around how file transfer operations will...

@wjcunningham7 I think this is an excellent addition as it transitions covalent from the indeterminate state it was during shutdown (before) to one that is well defined (workflow states being...

@cjao I think maybe there should be a sensible default for config manager type, and maybe instead of a function arg this could be an environment variable (maybe a commonly...