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
The latest Connect release allows you to opt-in to using uv to install packages on Connect by adding an entry to the manifest.json. Is there a way I can specify that in the publisher TOML such that it will pass through to the manifest (which I assume is being written on the fly?)
Related question: what happens if I generate a manifest with rsconnect-python and then use Publisher to publish?
The text was updated successfully, but these errors were encountered:
Is there a way I can specify that in the publisher TOML such that it will pass through to the manifest (which I assume is being written on the fly?)
You are correct that the manifest gets written on the fly when deploying. There isn't a way right now to write something in the config that gets passed plainly to the generated manifest without changes to the code.
Related question: what happens if I generate a manifest with rsconnect-python and then use Publisher to publish?
Publisher always uses the manifest it writes from the selected deployment / configuration combo, and does not use already created manifests.
For the new allow_uv attribute in the Python Package Manager section, in the current state of Publisher, we would have to add allow_uv as a configuration option and understand how to use it in our manifest generation
The latest Connect release allows you to opt-in to using
uv
to install packages on Connect by adding an entry to the manifest.json. Is there a way I can specify that in the publisher TOML such that it will pass through to the manifest (which I assume is being written on the fly?)Related question: what happens if I generate a manifest with
rsconnect-python
and then use Publisher to publish?The text was updated successfully, but these errors were encountered: