Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add custom labels to projects in Flyte control plane #474

Closed
1 of 13 tasks
kosigz-lyft opened this issue Aug 13, 2020 · 3 comments
Closed
1 of 13 tasks

Add custom labels to projects in Flyte control plane #474

kosigz-lyft opened this issue Aug 13, 2020 · 3 comments
Assignees
@kosigz-lyft
Labels
enhancement New feature or request
Milestone
0.8.0

Comments

@kosigz-lyft
Copy link
Contributor

kosigz-lyft commented Aug 13, 2020 •
edited
Loading

Motivation: Why do you think this is important?
Providing custom labels to projects will make it easier to attach metadata to Flyte projects in a scalable, general way that would benefit Lyft and other users.

Goal: What should the final outcome look like, ideally?
An ideal outcome would involve the Projects data to have a new field that can hold arbitrary K/V pairs for labeling projects, e.g. with contact information, escalation policy, etc.

Describe alternatives you've considered
Instead, we can store this metadata outside Flyte.

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other

Is this a blocker for you to adopt Flyte
No; Flyte is currently being used at Lyft.
@kosigz-lyft kosigz-lyft added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Aug 13, 2020
@kumare3 kumare3 mentioned this issue Aug 17, 2020
Merged
8 tasks
@kumare3 kumare3 removed the untriaged This issues has not yet been looked at by the Maintainers label Aug 17, 2020
@kumare3 kumare3 added this to the 0.7.0 milestone Aug 17, 2020
@kosigz-lyft
Copy link
Contributor Author

kosigz-lyft commented Aug 17, 2020 •
edited
Loading

flyteorg/flyteidl#77
flyteorg/flyteadmin#114

@kosigz-lyft
Copy link
Contributor Author

kosigz-lyft commented Aug 17, 2020 •
edited
Loading

👀 @EngHabu @kumare3 — updated issue with both PR's.

@kumare3 kumare3 modified the milestones: 0.7.0, 0.8.0 Sep 2, 2020
@anandswaminathan anandswaminathan modified the milestones: 0.8.0, 0.9.0 Sep 30, 2020
@kumare3 kumare3 modified the milestones: 0.9.0, 0.8.0 Oct 6, 2020
@kumare3
Copy link
Contributor

kumare3 commented Oct 6, 2020

This is part of 0.8.0 release

@kumare3 kumare3 closed this as completed Oct 8, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
@andrewwdye
Remove unused join condition (flyteorg#474)
5aecd67 
Signed-off-by: Andrew Dye <[email protected]>

Signed-off-by: Andrew Dye <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
@wild-endeavor
Remove legacy (flyteorg#474)
f2b7164 
Signed-off-by: Yee Hing Tong <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
@andrewwdye
Remove unused join condition (flyteorg#474)
3b258fe 
Signed-off-by: Andrew Dye <[email protected]>

Signed-off-by: Andrew Dye <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kosigz-lyft kosigz-lyft

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.8.0
Development

No branches or pull requests
3 participants
@kumare3 @anandswaminathan @kosigz-lyft