Support reading/writing Publisher `.posit/` deployment records (in addition to `rsconnect-python/*.json`)
Mantenedores costumam responder em até 1 dia
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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), includingserver_url, contentid/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-pythondetect 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/*.jsonbehavior 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
- Config:
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. |
- Linguagem predominante
- Python
- Estrelas
- 38
- Forks
- 28
- Merge médio
- 1d 7h
- PRs com merge (30d)
- 14
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de posit-dev/rsconnect-python
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
posit-dev/rsconnect-python#786 · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
posit-dev/rsconnect-python#543 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 72/100
posit-dev/rsconnect-python#513 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
posit-dev/rsconnect-python#178 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 45/100
posit-dev/rsconnect-python#872 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de posit-dev/rsconnect-python
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
omegaup/omegaup#10353 · 1 comentário ·
Mantenedores costumam responder em até 5 dias
-
bot-triaged module: LrScheduler module: optimizer triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
Mantenedores costumam responder em até 1 dia
-
documentation glm5 llm-model
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
vllm-project/vllm-ascend#19062 ·
Mantenedores costumam responder em até 1 dia
-
Author Page: shuai-zhao-llmAbertaauthor-page correction
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
acl-org/acl-anthology#10496 · 1 comentário ·
Mantenedores costumam responder em até 1 dia