Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Support reading/writing Publisher `.posit/` deployment records (in addition to `rsconnect-python/*.json`)

未關閉
  • 哪裡不對？
#829 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@mconflitti-pbc 已經在處理了。

開始於 2026年7月24日。

  • #830 來自 @mconflitti-pbc —— 未關閉

評估

這個 Issue 還沒有評估資料。

描述

Summary

rsconnect-python and the Posit Publisher (VS Code extension) currently track deployments in two mutually exclusive, incompatible formats. A directory deployed with one tool is invisible to the other, so the two toolchains can't collaborate on the same content. I'd like rsconnect-python to be able to read (and eventually write) the Publisher's .posit/ records so all of our deployment tooling speaks the same language.

Current behavior

Deploying the same app two ways produces two independent record sets that neither tool reconciles:

Publisher (.posit/publish/) — TOML, with a public versioned schema:

  • .posit/publish/<config>.toml — configuration (posit-publishing-schema-v3.json)
  • .posit/publish/deployments/<deployment>.toml — deployment record (posit-publishing-record-schema-v3.json), including server_url, content id/GUID, bundle_id, dashboard_url, direct_url, deployed files, requirements, etc.

rsconnect-python (rsconnect-python/<name>.json) — JSON keyed by server URL, with app_id, app_guid, app_url, app_mode, app_store_version.

Because rsconnect-python only knows about its own rsconnect-python/*.json store, a re-deploy via the CLI won't find or update the Publisher's record (and creates a separate piece of content rather than updating the existing one).

Requested behavior

  • On deploy/redeploy, have rsconnect-python detect an existing .posit/ directory and use those records to resolve the target server + existing content (GUID/id) for update-in-place.
  • Treat this as an addition, not a replacement of the existing rsconnect-python/*.json behavior initially, so we can begin transitioning without breaking existing workflows.
  • The Publisher schema is public and versioned, which makes it a good shared source of truth:
    • Config: https://cdn.posit.co/publisher/schemas/posit-publishing-schema-v3.json
    • Record: https://cdn.posit.co/publisher/schemas/posit-publishing-record-schema-v3.json

Why

The Publisher approach is considered the better/preferred way of recording deployments, and aligning rsconnect-python on it means the CLI, the VS Code extension, and other tooling share one deployment source of truth instead of drifting into incompatible records for the same content.

Related issues / prior art

# Repo · Issue State Why it's relevant
1 posit-dev/connect#36981 — feat: Support Publisher configuration files open The closest match. Proposes Connect natively consuming the Publisher .posit/ config + deployment-record TOML (same v3 schema) and building manifest.json from it — the server-side counterpart to making all tools speak the Publisher format.
2 posit-dev/publisher#3376 — feat: Integrate credential storage with rsconnect-python closed Direct precedent for Publisher ↔ rsconnect-python interoperability (sharing credential state). Shows the two tools are already being aligned; this issue extends the same idea to deployment records.
3 posit-dev/connect#29965 — Feat: Include provenance of deployment in metadata and UI open About tracking which tool/source produced a deployment — relevant to reconciling multiple record sources into one source of truth.
4 posit-dev/rsconnect-python#817 — Add support for publishing to Posit Connect Cloud open Adjacent: expands rsconnect-python's deployment targets/records, which intersects with how/where deployment state is stored.
主要語言
Python
星號
38
分支
28
平均合併
1 天 7 小時
30 天內合併 PR
14

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

posit-dev/rsconnect-python 的其他 Issue

查看 posit-dev/rsconnect-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。