David Legrand
David Legrand
The env var used for a task is `CC_RUN_COMMAND`, but maybe we can define it directly with a `--task COMMAND`.
Yes it's just another way to present already metadata (for SEO, especially Google) so it shouldn't be a problem
Could also be great to be able to renew auth before expiration. About expiration message, maybe plan first messages weeks before not only days.
As discussed internally, on this matter we should: - Show the expiry of the used token somewhere (`clever profile`, `clever diag`, both?) - Maybe tell the user when a token...
> I propose to do this in several steps (and maybe split issues): > > 1. date in `clever profile`, not sure about `clever diag` for now `clever profile` LGTM,...
ops team asked to implement a quite generic approach for this kind of option: - if the app is launched in a non-tty environment: no-color by default - if the...
Branch is rebased, I added JSON format support.
As API now supports env vars set at application creation, I use it. It allows me to set `CC_RUN_COMMAND` also in JSON mode (with no `human` message). We don't have...
> However the created app doesn't have a `CC_RUN_COMMAND` set. Maybe we should output an error for this case? I'm not sure to understand, as it's not an error. You...
`CC_RUN_COMMAND` is mandatory for Tasks, but I wouldn't force the user to set it within the app creation process (and I wasn't sure it will be a way to create...