-
Notifications
You must be signed in to change notification settings - Fork 427
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
Stack Request cleanup and improvements #2906
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add Documentation and Community
|
connector_config = ( | ||
existing_service_connector.configuration | ||
) | ||
connector_config[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is not a change of this PR, but do I understand this correctly: If someone creates a stack now that has any vm orchestrator in them, we secretly update the service connector to generate permanent tokens? That doesn't seem right on many levels, especially having such a flavor specific logic in the general implementation of this function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@schustmi is not wrong, this feels very specific and doesn't belong here. I guess this was required to make it easier to implement the stack creation wizard in the UI. Perhaps we can move this logic in the UI as well.
The design-wise correct solution for this is to make this behavior dynamic, so we don't have to configure it at all. The skypilot orchestrator would simply ask the service connector explicitly to not generate temporary tokens. This is just some technical debt we inherited when we implemented the SkyPilot orchestrators. Perhaps I can pitch in this part of the implementation, doesn't seem to difficult.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was just pointing this out, I don't we think we have to do that as part of this PR. Is it okay if I create a ticket for you @stefannica?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, thanks !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦭
Describe changes
WIP.
WARNING: This will require a lot of dashboard changes. Do NOT merge before contacting the frontend team.
Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes