Stephen
04/01/2022, 9:48 AMlatest
for scheduled workflows? It’d be useful for us so that we wouldn’t have to archive/ activate launchplans for each change.Prafulla Mahindrakar
04/01/2022, 12:56 PMtype LaunchPlanKey struct {
Project string `gorm:"primary_key;index:lp_project_domain_name_idx,lp_project_domain_idx" valid:"length(0|255)"`
Domain string `gorm:"primary_key;index:lp_project_domain_name_idx,lp_project_domain_idx" valid:"length(0|255)"`
Name string `gorm:"primary_key;index:lp_project_domain_name_idx" valid:"length(0|255)"`
Version string `gorm:"primary_key" valid:"length(0|255)"`
}
which is combination of all project-domain-name-version
Now with what you are saying only one such entity can be having latest version . So no new changes can be used for latest version and that won’t work. Each launchplan entity with its version is also immutable.
Also if we use another field as an alias for latest , still we would have stop old running latest and start running the new latest.Ketan (kumare3)
Stephen
04/01/2022, 1:29 PMflytectl update launchplan
section but maybe it’s something else?
https://docs.flyte.org/projects/flytectl/en/latest/gen/flytectl_update_launchplan.htmlKetan (kumare3)
Stephen
04/01/2022, 1:31 PMPrafulla Mahindrakar
04/01/2022, 1:33 PMkatrina
Stephen
04/04/2022, 8:21 AMKetan (kumare3)
Prafulla Mahindrakar
04/07/2022, 5:04 AMStephen
04/07/2022, 10:20 AMPrafulla Mahindrakar
04/07/2022, 12:17 PMKetan (kumare3)
Stephen
04/07/2022, 2:11 PMKetan (kumare3)
Prafulla Mahindrakar
04/07/2022, 3:59 PM