markdown-confluence / markdown-confluence

Publish your Markdown Files to Confluence

Home Page:https://markdown-confluence.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error: No Paths Provided -- .markdown-confluence.json folderToPublish not being used properly?

symplrdudley opened this issue · comments

Issue Description

I am trying to publish an Azure DevOps Wiki from Markdown that was exported into Confluence. Aside from the requirement of files and folders to be uniquely named, I tried with a fresh folder and file structure. I still received the Error: No Paths Provided error (because it was red).

However, when I leave folderToPublish as just . or current directory, it works just fine. I then have to control where I'm getting my markdown files from by setting the contentRoot key.

❓ Why does anything other than "folderToPublish": "." seem to cause this issue?

I also have other issues like index.md not seemingly being published? That's a different ticket.

Evidence

The Error
➜  grc-docs-wiki git:(main) ✗
./markdown-container.sh
┌──────────────────────────────┐
│                              │
│   Error: No Paths Provided   │
│                              │
└──────────────────────────────┘
Bash script to run container
#!/usr/bin/env bash
#

export ATLASSIAN_API_TOKEN=$(cat .apitoken)
podman run \
  --interactive \
  --tty \
  --rm \
  --mount="type=bind,source=$(pwd),destination=/content,relabel=shared" \
  --userns=keep-id \
  --env="ATLASSIAN_API_TOKEN" \
  ghcr.io/markdown-confluence/publish:latest \
    "${@}"
.markdown-confluence.json
{
    "confluenceBaseUrl": "https://symplr.atlassian.net",
    "confluenceParentId": "274570412556",
    "atlassianUserName": "pdudley@symplr.com",
    "contentRoot": "./phil/",
    "folderToPublish": "thingy",
    "firstHeadingPageTitle": true
}
The folder structure
➜  grc-docs-wiki git:(main) ✗
tree phil
phil
├── index.md
└── thingy
    ├── dude
    │   └── stuff
    └── mydude.md

4 directories, 2 files

I experienced the same issue. It was quite confusing. This issue at least let me know how to get it working to test.