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

[Core feature] Allow flytectl to set a targetExecutionCluster #5395

Closed
2 tasks done
RRap0so opened this issue May 20, 2024 · 1 comment · Fixed by #5394
Closed
2 tasks done

[Core feature] Allow flytectl to set a targetExecutionCluster #5395

RRap0so opened this issue May 20, 2024 · 1 comment · Fixed by #5394
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@RRap0so
Copy link
Contributor

RRap0so commented May 20, 2024

Motivation: Why do you think this is important?

As a follow-up from #5081 this PR adds the ability in flytectl for the user to specify a targetExecutionCluster when creating an execution.

Goal: What should the final outcome look like, ideally?

A user can trigger an execution with flytectl in whatever cluster they want.

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

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

  • Yes

Have you read the Code of Conduct?

  • Yes
@RRap0so RRap0so added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels May 20, 2024
Copy link

runllm bot commented May 20, 2024

To allow flytectl to set a targetExecutionCluster, you need to add support for specifying the ExecutionClusterLabel when creating an execution. This feature enables users to direct executions to specific clusters without being tied to a Project/Domain.

Would you like more detail on how to implement this in flytectl?

Sources:


This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

@RRap0so RRap0so mentioned this issue May 20, 2024
3 tasks
@eapolinario eapolinario added good first issue Good for newcomers and removed untriaged This issues has not yet been looked at by the Maintainers labels May 23, 2024
@eapolinario eapolinario self-assigned this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants