Skip to content

Conversation

@un-def
Copy link
Collaborator

@un-def un-def commented Dec 8, 2025

  • Deprecate and ignore RunCollection.get_run_plan() repo_dir argument
  • Ensure UsersAPIClient.get_my_user() returns UserWithCreds
  • Ensure UserSSHKeyManager.get_user_key() returns user SSH key stored on the server
  • Drop SSH key-related support code for pre-0.20.0 servers

* Deprecate and ignore RunCollection.get_run_plan() repo_dir argument
* Ensure UsersAPIClient.get_my_user() returns UserWithCreds
* Ensure UserSSHKeyManager.get_user_key() returns user SSH key stored on
  the server
* Drop SSH key-related support code for pre-0.20.0 servers
" automatically replicated to all clients.",
)
ssh_key_pub = config_manager.dstack_key_path.with_suffix(".pub").read_text()
# Ensure we have a fresh key locally
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@un-def Sorry, just to confirm, why do we need the key locally when submitting a run? I thought we only need it when attaching to a run, no?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, both /get_plan and /apply endpoints generate the user key if missing, we don't need to trigger key generation manually. I've removed this redundant API call, added /get_plan/apply tests, and simplified server code a bit : 329e993

@un-def un-def merged commit 376be2a into master Dec 9, 2025
28 checks passed
@un-def un-def deleted the pr_api_clients_cleanup branch December 9, 2025 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants