Skip to content

Support the Quarto knitr engine when deploying content #786

Description

@amol-

Goal

Allow content using the Quarto knitr engine to be deployed and to have a
manifest written. Today validate_quarto_engines (rsconnect/actions.py) accepts
only markdown and jupyter and rejects everything else, including knitr.

Why

knitr is the default Quarto engine for documents that mix R and Python chunks.
Now that rsconnect-python can carry R dependencies from renv.lock, the original
reason for excluding knitr no longer applies, so the rejection blocks a case
the tool can otherwise handle. Raised in review:
#785 (comment)

References

  • rsconnect/actions.py (validate_quarto_engines) — the engine allowlist.
  • rsconnect/main.py — the four Quarto entry points already branch on
    "jupyter" in engines and handle the no-Python-environment case (markdown).
  • renv.lock R-dependency support: PR: support for parsing renv.lock support for parsing renv.lock #785

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions