SeungTaeKim
08/17/2022, 6:03 AMSamhita Alla
https://<url_domain>/api/v1/workflows/<project>/<domain>/<wf>/<version>
?SeungTaeKim
08/17/2022, 6:27 AMSamhita Alla
SeungTaeKim
08/17/2022, 6:31 AMnot found
the same messageSamhita Alla
Prafulla Mahindrakar
08/17/2022, 6:35 AMSeungTaeKim
08/17/2022, 7:17 AMPrafulla Mahindrakar
08/17/2022, 7:24 AMflytectl update workflow-meta -p flytesnacks -d development flyte_project_template.mlflow_flyte_test.mlflow_wf --activate
SeungTaeKim
08/17/2022, 7:29 AMunknown flag
. Are you talking to the commands like workflow-execution-config
or workflow-meta
??Prafulla Mahindrakar
08/17/2022, 7:29 AMSeungTaeKim
08/17/2022, 7:29 AMnot found
, the same error of console uiPrafulla Mahindrakar
08/17/2022, 7:32 AMSeungTaeKim
08/17/2022, 7:33 AM- name: Create project
run: |
flytectl create project --name ${{ env.FLYTE_PROJECT }} --id ${{ env.FLYTE_PROJECT }} || true
if [ !-z "${{ env.FLYTE_DESCRIPTION }}" ]; then
flytectl update project -p ${{ env.FLYTE_PROJECT }} --description ${{ env.FLYTE_DESCRIPTION }}
fi
- name: Archive launchplans
run: |
(flytectl get launchplan -p {{ $env.FLYTE_PROJECT }} -d {{ $env.FLYTE_DOMAIN }} -o json || echo "") | jq -rc 'if type=="array" then map(.id)[] else .id end' | while read id; do
name=$(echo $id | jq -r .name)
version=$(echo $id | jq -r .version)
flytectl update launchplan $name -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version $version --archive
done
- name: Serialize project
run: |
mkdir _pb_output
echo pyflyte --pkgs ${{ env.PROJECT_NAME }} serialize --local-source-root . --image ${{ env.IMAGE_TAG }} workflows -f _pb_output/
pyflyte --pkgs ${{ env.PROJECT_NAME }} serialize --local-source-root . --image ${{ env.IMAGE_TAG }} workflows -f _pb_output/
- name: Register serialized project
run: |
flytectl register files _pb_output/* -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version ${{ env.VERSION }}
- name: Activate launchplans
run: |
tomlq -rc '.qraft.flyte.active_launch_plans[]' pyproject.toml | while read name; do
flytectl update launchplan $name -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version ${{ env.VERSION }} --activate
done
Prafulla Mahindrakar
08/17/2022, 7:35 AMSeungTaeKim
08/17/2022, 7:40 AMPrafulla Mahindrakar
08/17/2022, 7:41 AMhttps://flyte-org.slack.com/files/U03HPGSLZN3/F03TYFM2NQ2/screenshot_from_2022-08-17_14-25-24.png▾
SeungTaeKim
08/17/2022, 7:48 AMflytesnacks
into flyte-project-template
, and CLI returns successfully updated
.
but the the launch plan button is still deactivatedPrafulla Mahindrakar
08/17/2022, 7:52 AMSeungTaeKim
08/17/2022, 7:56 AMSamhita Alla
SeungTaeKim
08/17/2022, 8:43 AMSamhita Alla
flytectl get launchplan -p <project> -d <domain> <wf>
flytectl update launchplan -p <project> -d <domain> <name_of_lp> --version <version> --activate
Just wondering if launch plan + version flag would work.Prafulla Mahindrakar
08/17/2022, 10:47 AMSeungTaeKim
08/17/2022, 1:53 PMNot Found
, so I guess Flyte admin does not found the registration file (The path is registered with CLI, but not file)
I think I should check where the filed gone tomorrowNot Found
error I mentioned yesterday.
It was the problem of version name, which have not to contain /
in version name.
as @Samhita Alla mentioned on https://flyte-org.slack.com/archives/CNMKCU6FR/p1660717490719359?thread_ts=1660716204.783219&cid=CNMKCU6FR, I think Flyte call the registered filed through API, so if the version name include slash, it interprets wrong path.
I have spend 2 days to solve this.
Thank you all