-
Notifications
You must be signed in to change notification settings - Fork 17
Implements Posit Workbench Launcher #322
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
2fd98e3 to
370dae3
Compare
shikokuchuo
left a comment
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.
This PR is now in a ready state for merge if not exposing any configurable options.
72c7c4d to
88c9a8a
Compare
9829470 to
8a84bc3
Compare
49458cf to
8655ae5
Compare
|
This PR has been superseded by #553. We still provide for zero-config that will 'just work' for those in Posit Workbench environments, but open this up to any platform that offers job launches via an HTTP API endpoint. This approach avoids use of any |
Closes #321.
Adds dedicated
posit_workbench_config()to create a remote launch configuration for Posit Workbench.Currently only supports Rstudio Pro sessions as this uses the
.rsinternal namespace functions rather than the Workbench REST API, which is still experimental.Usage:
Automatically launches daemons on the default configured Kubernetes / traditional cluster.
Update: