Rsconnect-python

Changed

Corrected changelog heading.

Added

- You can now set environment variables for the deployed content with the `-E` option.
These will be passed to RStudio Connect during the deployment process,
so they are available in your code whenever it runs within RStudio Connect.
Requires RStudio Connect version 1.8.6 or later.

- You can now deploy Quarto projects. This requires RStudio Connect release
2021.08.0 or later. Use `rsconnect deploy quarto` to deploy, or `rsconnect
write-manifest quarto` to create a manifest file.

- An `image` command line option has been added to the `write-manifest` and
`deploy` commands to specify the target image to be used on the RStudio Connect
server during content execution. This is only supported for the `api`, `bokeh`, `dash`,
`fastapi`, `notebook`, `quarto` and `streamlit` sub-commands. It is only
applicable if the RStudio Connect server is configured to use off-host execution.

- You can now deploy static content such as html and its associated assets with
`rsconnect deploy html`.

Added

- Publish supported python versions announcement.

Added

- Adds `rsconnect content` subcommands for interacting with RStudio Connect's `/v1/content`
REST API. This allows users to search, download, and (re)build content. Users should
note that the `rsconnect content build` subcommand requires RStudio Connect release 2021.11.1
or later.

Changed

- Support for Python 2.7 has been removed in this release.

Added

- You can now deploy FastAPI applications. This requires RStudio Connect release 2021.08.0
or later. Use `rsconnect deploy fastapi` to deploy, or `rsconnect write-manifest fastapi`
to create a manifest file.
- In addition to FastAPI, you can also deploy Quart, Sanic, and Falcon ASGI applications.

Changed

- rsconnect-python will now issue a warning during deployment if there isn't a requirements.txt
file in the deployment directory. Using a requirements file ensures consistency in the
environment that will be created by the RStudio Connect server during deployment. This helps avoid
unnecessary package installations and issues that can occur if rsconnect-python falls back
to inferring packages from the local Python environment.

Added

- If an entrypoint is not specified with `--entrypoint`, rsconnect-python will attempt
to choose an entrypoint file. It looks for common names (`app.py`, `application.py`,
`main.py`, `api.py`). If there is a single python source file in the directory,
that will be used as the entrypoint.
rsconnect-python does not inspect the file contents to identify the object name, which must be
one of the default names that Connect expects (`app`, `application`, `create_app`, or `make_app`).

- Ability to hide code cells when rendering Jupyter notebooks.

After setting up Connect (>=1.9.0) and rsconnect-python, the user can render a Jupyter notebook without its corresponding code cells by passing the ' hide-all-input' flag through the rsconnect cli:


rsconnect deploy notebook \
--server https://connect.example.org:3939 \
--api-key my-api-key \
--hide-all-input \
mynotebook.ipynb


To selectively hide the input of cells, the user can add a tag call 'hide_input' to the cell, then pass the ' hide-tagged-input' flag through the rsconnect cli:


rsconnect deploy notebook \
--server https://connect.example.org:3939 \
--api-key my-api-key \
--hide-tagged-input \
mynotebook.ipynb