acoustic-carpenter-78188
10/03/2023, 2:07 AMbase_exec_id unless it is already added
Pull request opened by eapolinario
TL;DR
Automatically adds base_exec_id label with the value of current execution or a previous base_exec_id if it exists.
Reasons:
1. Make it possible to retrieve all executions launched by the same base execution id (even recursively)
2. users could group executions using their own base exec id
3. flytectl get executions or remote list executions can use this label as a filter to retrieve high level progress of all subworkflows
Type
☐ Bug Fix
☑︎ Feature
☐ Plugin
Are all requirements met?
☑︎ Code completed
☐ Smoke tested
☑︎ Unit tests added
☑︎ Code documentation added
☑︎ Any pending items have an associated Issue
flyteorg/flyte
GitHub Actions: Integration Test (flyteadmin) / Integration tests
GitHub Actions: Unit Tests (flytestdlib) / Run Unit Test
GitHub Actions: Unit Tests (flytepropeller) / Run Unit Test
GitHub Actions: Unit Tests (flyteplugins) / Run Unit Test
GitHub Actions: Unit Tests (flytecopilot) / Run Unit Test
GitHub Actions: Unit Tests (flyteadmin) / Run Unit Test
GitHub Actions: Unit Tests (datacatalog) / Run Unit Test
GitHub Actions: Lint (flytestdlib) / Run Lint
GitHub Actions: Lint (flytepropeller) / Run Lint
GitHub Actions: Lint (flyteplugins) / Run Lint
GitHub Actions: Lint (flyteidl) / Run Lint
GitHub Actions: Lint (flyteadmin) / Run Lint
GitHub Actions: Lint (datacatalog) / Run Lint
GitHub Actions: Check Go Generate (flytepropeller) / Go Generate
GitHub Actions: Check Go Generate (flytecopilot) / Go Generate
GitHub Actions: Check Go Generate (flyteadmin) / Go Generate
GitHub Actions: Check Go Generate (datacatalog) / Go Generate
GitHub Actions: compile
✅ 12 other checks have passed
12/30 successful checks