[Feature] Validation of Flyte fields to create new projects #519
Labels
enhancement
New feature or request
stale
untriaged
This issues has not yet been looked at by the Maintainers
Comments
kosigz-lyft
added
enhancement
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
* fix: cache icon fro map task * fix: icon and text center Signed-off-by: eugenejahn <[email protected]>
|
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏 |
|
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏 |
|
Labels are already supported on flyte, https://docs.flyte.org/projects/cookbook/en/latest/auto_examples/productionizing/workflow_labels_annotations.html#adding-workflow-labels-and-annotations |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation: Why do you think this is important?
In a previous PR, I added the capability for teams using Flyte to inject custom labels onto their projects, e.g. "slack" => "#machinelearning" or "email" => "[email protected]". This is useful for adding metadata to projects. However, one problem we have observed is that it's difficult to keep these labels up to date (and populated) if there is not some logic that organizations can add to the Flyte Admin control plane to disallow creation of new projects should labels not be included.
Goal: What should the final outcome look like, ideally?
A generic piece that organizations can use to add validation to the labels on a Flyte project. e.g. being able to require that all projects in your organization have a Slack channel attached.
Describe alternatives you've considered
The alternative is to build an external system to Flyte that monitors for changes, i.e. new projects without a Slack, and alerts.
Flyte component
[Optional] Propose: Link/Inline
Draft: flyteorg/flyteadmin#119
Is this a blocker for you to adopt Flyte
This feature will be very useful.
The text was updated successfully, but these errors were encountered: