Releases: Netflix/metaflow
2.17.1
What's Changed
- Bump tmp from 0.2.3 to 0.2.4 in /metaflow/plugins/cards/ui by @dependabot[bot] in #2536
- fix: metaflow-dev improvements by @saikonen in #2527
- [bug fix] fix subtle bug from #2463 by @valayDave in #2540
- Fix bug in deployer reload logic by @talsperre in #2533
- patch release by @savingoyal in #2541
- [bug fix] fix subtle bug from #2463 by @valayDave in #2542
- Fix bug in metaflow version when
public=True
by @talsperre in #2539
Full Changelog: 2.17.0...2.17.1
2.17.0
Improvements
Argo Workflows name length restriction
This release introduces a limit to the workflow name lengths that are deployed to Argo Workflows.
Why was this necessary?
Argo Workflows attaches the workflow template name (the deployed flow name) as a label to the Kubernetes resources it creates when argo itself launches a flow (events, schedule, Argo UI). The problem is that Kubernetes labels have a maximum length of 63 characters, and if a workflow name is longer than that, it will fail to launch due to not fitting in the label.
Launching flows on Argo Workflows through the Metaflow CLI has always been exempt of this issue, as this has not tried to attach such a label to the resources.
What about existing flows?
Existing flows continue to operate as previously, and these can still be operated on with the Metaflow CLI commands, e.g. argo-workflows trigger
/argo-workflows delete
.
An existing flow will always be replaced when running argo-workflows create
. With the new version this might also result in a differently named deployment, in case the old one had a name that was too long.
What happens with long names now?
When using the @project
decorator, Metaflow will automatically truncate the deployed name if it is too long. A part of each name partial (project / branch / flow_name
) is kept to help with finding the deployments in Argo UI.
If the name of the deployment is too long when deploying without @project
, then this is treated as an error and it is up to the user to provide a shorter name. This can be done by either renaming the flow class, or by supplying a custom name with --name
Deploying the same flow with an older version of Metaflow will lead to two separate deployments existing at once if the length of the name exceeded the limit.
For such flows be sure to only deploy them with Metaflow versions >=2.17 or use the --name
CLI option to specify a custom deploy name.
What's Changed
- [cards] add attempt to default card. by @valayDave in #2532
- address name contraction issues in argo-workflows create by @savingoyal in #2082
- release: 2.17.0 by @saikonen in #2535
Full Changelog: 2.16.8...2.17.0
2.16.8
What's Changed
- [argo] Fix eventing for
@parallel
based workflow by @valayDave in #2516 - patch release by @savingoyal in #2529
Full Changelog: 2.16.7...2.16.8
2.16.7
What's Changed
- get_triggered_run for argo by @mt-ob in #2522
- fix up imghdr import by @savingoyal in #2524
- add wrapping to echo by @savingoyal in #2523
- Fix/runner packaging by @romain-intel in #2507
- vendor pure pythonic pyyaml by @savingoyal in #2525
- patch release by @savingoyal in #2526
Full Changelog: 2.16.6...2.16.7
2.16.6
What's Changed
- backward compatibility for generate_fake_flow_file_contents by @mt-ob in #2511
- [bug fix] fix subtle bug from #2463 by @valayDave in #2513
- Bump form-data from 4.0.2 to 4.0.4 in /metaflow/plugins/cards/ui by @dependabot[bot] in #2514
- patch release by @savingoyal in #2517
Full Changelog: 2.16.5...2.16.6
2.16.5
What's Changed
- Fixes tolerations typehint by @Winterflower in #2502
- add
list_deployed_flows
for argo by @mt-ob in #2508 - [cards] remove imghdr warnings by @valayDave in #2509
- patch release by @savingoyal in #2510
New Contributors
- @Winterflower made their first contribution in #2502
Full Changelog: 2.16.4...2.16.5
2.16.4
What's Changed
- [bug fix] fix subtle bug from #2463 by @valayDave in #2498
- patch release by @savingoyal in #2500
Full Changelog: 2.16.3...2.16.4
2.16.3
2.16.2
What's Changed
- retry 500s too for service by @savingoyal in #2493
- fix: kubernetes imagePullSecrets support for argo workflows by @saikonen in #2494
- patch release by @savingoyal in #2495
Full Changelog: 2.16.1...2.16.2