10000
Implement flags for targeting an execution environment during deployment · Issue #1147 · rstudio/rsconnect · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connect 2025.04 allows setting environment.identifier in the bundle's manifest.json. This new field allows the content to target a specific execution environment when running on Connect. The existing environment.image field remains unchanged however the semantics are slightly different. An image selection is now treated the same as any other piece of matching criteria. Connect will choose any execution environment that uses the specified container image.
We should add an environment_id flag to both deployApp and writeManifest - the value is the guid of the target execution environment in Connect and it should be written to environment.identifier in the manifest.json.
We should also add arguments the following arguments to deployApp: default_image and default_environment_id. These arguments accepts an image name and an execution environment guid respectively, however instead of writing these to the manfiest.json, we should update the App record in Connect to set the app.default_image_name and app.default_environment_guid fields. This new workflow allows users to call deployApp(..., default_image='my/custom/image:latest') or deployApp(..., default_environment_id='<env-guid>') only once and the image/environment will continue to be used for subsequent deployments (as long as it isn't overwritten by another deployment). This means that the arguments doesn't need to be provided everytime deployApp(...) is called which is how the current image argument behaves. This is the same workflow used by the Connect dashboard.
The text was updated successfully, but these errors were encountered:
Connect 2025.04 allows setting
environment.identifierin the bundle'smanifest.json. This new field allows the content to target a specific execution environment when running on Connect. The existingenvironment.imagefield remains unchanged however the semantics are slightly different. Animageselection is now treated the same as any other piece of matching criteria. Connect will choose any execution environment that uses the specified container image.We should add an
environment_idflag to bothdeployAppandwriteManifest- the value is the guid of the target execution environment in Connect and it should be written toenvironment.identifierin the manifest.json.We should also add arguments the following arguments to
deployApp:default_imageanddefault_environment_id. These arguments accepts an image name and an execution environment guid respectively, however instead of writing these to the manfiest.json, we should update the App record in Connect to set theapp.default_image_nameandapp.default_environment_guidfields. This new workflow allows users to calldeployApp(..., default_image='my/custom/image:latest')ordeployApp(..., default_environment_id='<env-guid>')only once and the image/environment will continue to be used for subsequent deployments (as long as it isn't overwritten by another deployment). This means that the arguments doesn't need to be provided everytimedeployApp(...)is called which is how the currentimageargument behaves. This is the same workflow used by the Connect dashboard.The text was updated successfully, but these errors were encountered: