quarto-dev / quarto-dev/quarto-cli
publish to Confluence with params
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Discussed in https://github.com/quarto-dev/quarto-cli/discussions/9830
Originally posted by hutch3232 May 31, 2024
Description
Firstly, I wanted to mention that I found this related discussion: https://github.com/quarto-dev/quarto-cli/discussions/5310
In that discussion, it sounded like the recommended approach (until publish inherits from render) is to do a two-stage approach: first rendering the document with parameters supplied and then to publish using the --no-render option.
Unfortunately, when I tried to do that I get:
ERROR: Confluence requires rendering before publish
My code:
quarto render confl.qmd -P myvar:"test"
quarto publish confluence --no-render confl.qmd
Am I approaching this wrong? Is it possible to pass render-time parameters to a Confluence-bound .qmd?
quarto --version
1.4.550
Ubuntu 20.04
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported workflow with quarto render confl.qmd -P myvar:"test" followed by quarto publish confluence --no-render confl.qmd. Read discussions 9830 and 5310 for the intended parameter and publish behavior. Done means the supported workflow is identified and the Confluence publish path no longer rejects the pre-rendered document, or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100