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.

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

[FlyteCTL Feature] kubectl-like configuration from multiple files #6237

Open
2 tasks done
granthamtaylor opened this issue Feb 10, 2025 · 0 comments
Open
2 tasks done
Assignees
Labels
backlogged For internal use. Reserved for contributor team workflow. enhancement New feature or request help wanted Extra attention is needed

Comments

@granthamtaylor
Copy link

Describe the feature/command for FlyteCTL

Applying multiple configurations can be quite painful, especially over multiple projects / domains.

For example:

flytectl workflow-execution-config --file manifest.yaml

kind: workflow-execution-config
domain: development
project: protein-design
attributes:
    projectQuotaCpu: "1000"
    projectQuotaMemory: 10Ti
workflow_execution_config:
    security_context:
        run_as: [email protected]

Provide a possible output or UX example

Instead, one should be able to reference a yaml file, or multiple files, or a directory of files, and apply them all simultaneously via flytectl -f manifest.yaml

Please see that we are specifying the kind in reach file, as opposed to defining it as a CLI arg.

---
kind: project
name: protein-design
id: protein-design
---
kind: workflow-execution-config
domain: development
project: protein-design
attributes:
    projectQuotaCpu: "1000"
    projectQuotaMemory: 10Ti
workflow_execution_config:
    security_context:
        run_as: [email protected]
---
kind: workflow-execution-config
domain: production
project: protein-design
attributes:
    projectQuotaCpu: "2000"
    projectQuotaMemory: 20Ti
workflow_execution_config:
    security_context:
        run_as: [email protected]

This is analogous to how kubectl works.

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@granthamtaylor granthamtaylor added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Feb 10, 2025
@eapolinario eapolinario added help wanted Extra attention is needed and removed untriaged This issues has not yet been looked at by the Maintainers labels Feb 13, 2025
@eapolinario eapolinario self-assigned this Feb 13, 2025
@eapolinario eapolinario added the backlogged For internal use. Reserved for contributor team workflow. label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlogged For internal use. Reserved for contributor team workflow. enhancement New feature or request help wanted Extra attention is needed
Projects
Status: Backlog
Development

No branches or pull requests

2 participants