Rsconnect-python

Added

- The `CONNECT_TASK_TIMEOUT` environment variable, which configures the timeout for [task based operations](https://docs.posit.co/connect/api/#get-/v1/tasks/-id-). This value translates into seconds (e.g., `CONNECT_TASK_TIMEOUT=60` is equivalent to 60 seconds.) By default, this value is set to 86,400 seconds (e.g., 24 hours).
- Deploys for Posit Cloud now support Quarto source files or projects with `markdown` or `jupyter` engines.

Added
- Deploys for Posit Cloud and shinyapps.io now accept the `--visibility` flag.

Changed
- Removes redundant client-side compatibility checks in favor of server-side compatibility checks when deploying Python content. Note that the error handling may differ between versions of Connect. See Connect release notes for additional details regarding compatibility.

Fixed
- Shiny app deployment fails when static content is present in the app [373](https://github.com/posit-dev/rsconnect-python/issues/373).

Added
- `deploy html` and `deploy manifest` now support deployment to Posit Cloud.

- Added `system caches list` and `system caches delete` commands which allow administrators to enumerate and delete R and Python runtime caches from Connect servers [384](https://github.com/posit-dev/rsconnect-python/pull/384). Read more about the feature in our [docs](https://docs.posit.co/connect/admin/server-management/runtime-caches/).

Changed
- Cloud deployments accept the content id instead of application id in the --app-id field.
- The `app_id` field in application store files also stores the content id instead of the application id.
- Application store files include a `version` field, set to 1 for this release.

Fixed
- cacert read error when adding/updating a server [403](https://github.com/posit-dev/rsconnect-python/issues/403).
- getdefaultlocale no longer work with newer versions of Python [397](https://github.com/posit-dev/rsconnect-python/issues/397) [#399](https://github.com/posit-dev/rsconnect-python/issues/399).
- extra files not being included in write-manifest [416](https://github.com/posit-dev/rsconnect-python/issues/416).

Added
- The `CONNECT_REQUEST_TIMEOUT` environment variable, which configures the request timeout for all blocking HTTP and HTTPS operations. This value translates into seconds (e.g., `CONNECT_REQUEST_TIMEOUT=60` is equivalent to 60 seconds.) By default, this value is 300.

Fixed

- Extra files were not being included in deploy Voila.

- Error message to indicate the Python also has to be configured in Connect.

Added
- Added `deploy voila` command to deploy Jupyter Voila notebooks. See the [user documentation](https://docs.posit.co/connect/user/publishing-cli-notebook/#interactive-voila-deployment)
for more information.

Changed
- `deploy html` was refactored. Its behavior is described below.

Deploying HTML
Specifying a directory in the path will result in that entire directory*, subdirectories, and sub contents included in the deploy bundle. The entire directory is included whether or not an entrypoint was supplied


e.g.
using the following directory,

├─ my_project/
│ ├─ index.html
│ ├─ second.html

and the following command:

rsconnect deploy html -n local my_project

or this command:

rsconnect deploy html -n local my_project -e my_project/index.html

we will have a bundle which includes both `index.html` and `second.html`

- specifying a file in the path will result in that file* - not the entire directory - included in the deploy bundle

e.g.
using the following directory,

├─ my_project/
│ ├─ index.html
│ ├─ second.html

and the following command:

rsconnect deploy html -n local my_project/second.html

we will have a bundle which includes `second.html`

- a note regarding entrypiont
- providing an entrypoint is optional if there's an `index.html` inside the project directory, or if there's a *single* html file in the project directory.
- if there are multiple html files in the project directory and it contains no `index.html`, we will get an exception when deploying that directory unless an entrypoint is specified.

- if we want to specify an entrypint, and we are executing the deploy command outside a project folder, we must specify the full path of the entrypoint:


rsconnect deploy html -n local my_project -e my_project/second.html


- if we want to specify an entrypint, and we are executing the deploy command inside the project folder, we can abbreviate the entrypoint, like so:

cd my_project
rsconnect deploy html -n local ./ -e second.html



*Plus the manifest & other necessary files needed for the bundle to work on Connect.