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.

Sign up for GitHub

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

Jump to bottom

migrate to click #45

Closed
cornelinux opened this issue Apr 13, 2020 · 0 comments · Fixed by #47
Closed

migrate to click #45

cornelinux opened this issue Apr 13, 2020 · 0 comments · Fixed by #47
Milestone
3.0 smartcards

Comments

@cornelinux
Copy link
Member

I think we should migrate the privacyidea admin client to click.

I looked at adding a functionality (#42) to the command line client and realized, this is bloated.
We need to restructure the client, so why not move?
And choose a modular approach, e.g. like ykman to keep file sizes low.

Also click is the successor for flask_script, which we use for pi-mange in the backend, so we need to get used to click anywas.
@cornelinux cornelinux added this to the 3.0 smartcards milestone Apr 13, 2020
cornelinux added a commit that referenced this issue Apr 14, 2020
@cornelinux
Migrate to click framework
255ed18 
The click framework is a new framework for command line
interfaces. We use a file for each command in
the commands/ directory to keep things easier to manage.

We add a new command section "certificate" - although it
is a tokentype, but this makes creating certificates, CSRs...
easier.

Closes #45
Closes #44
@cornelinux cornelinux mentioned this issue Apr 14, 2020
Merged
@laclaro laclaro mentioned this issue Nov 6, 2020
Closed
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
3.0 smartcards
Development

Successfully merging a pull request may close this issue.

Migrate to click framework privacyidea/privacyideaadm
1 participant
@cornelinux