We should document the dataflow naming... ✨ conventions ✨

leap-stc / data-and-compute-team

Repo to organize issues/mangagment of the LEAP Data and Computation Team

Apache License 2.0

1 stars 0 forks source link

We should document the dataflow naming... ✨ conventions ✨ #11

Open norlandrhagen opened 2 months ago

norlandrhagen commented 2 months ago

Maybe in the template repo: https://github.com/leap-stc/LEAP_template_feedstock or somewhere in @jbusecke's revised docs.

jbusecke commented 2 months ago

Just to clarify, this is for 'how to kick of a dataflow job from the feedstock'?

norlandrhagen commented 2 months ago

I probably should have added more details haha. This was more just some guidelines on the rules dataflow requires for recipe ID naming. _, uppercase etc.

norlandrhagen commented 2 months ago

Speaking of.. ValueError: job_name must match the regex ^[a-z][-_0-9a-z]***0,62***$, instead found eNATL60-BLBT02-pyramid-10306991809-1 👎

jbusecke commented 2 months ago

Ah yes, this is sooo annoying. Actually we should bring this up on Friday for discussion re what to maintain about runner.