Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nbconvert exporter entrypoint #3

Open
mpacer opened this issue Feb 27, 2018 · 1 comment · May be fixed by #9
Open

Nbconvert exporter entrypoint #3

mpacer opened this issue Feb 27, 2018 · 1 comment · May be fixed by #9

Comments

@mpacer
Copy link

mpacer commented Feb 27, 2018

You can expose this package directly to nbconvert (so you could use jupyter nbconvert --to confluence your.ipynb) using entrypoints:

For example (from the docs):

setup(
    ...
    entry_points = {
        'nbconvert.exporters': [
            'simple = mymodule:SimpleExporter',
            'detail = mymodule:DetailExporter',
        ],
    }
)
@parente
Copy link
Contributor

parente commented Mar 1, 2018

With the current implementation, the minimum required parameters on the command line for the exporter entrypoint command line would be the following:

nbconvert --to confluence --ConfluenceExporter.url=<url of the page to update> \
  --ConfluenceExporter.username=<username> --ConfluenceExporter.password=<password> \
  mynotebook.ipynb

Specifying a password on the command line is not great for securty, so we'd probably need to move the code that reads it from an env var or the .nbconflux file to the exporter. That would make the minimum command line:

nbconvert --to confluence --ConfluenceExporter.url=<url of the page to update> mynotebook.ipynb

@parente parente linked a pull request Mar 18, 2018 that will close this issue
2 tasks
This was referenced Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants