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

apostrophe-users:add does not work via cli tool #13

Open
benirose opened this issue Jun 9, 2017 · 7 comments
Open

apostrophe-users:add does not work via cli tool #13

benirose opened this issue Jun 9, 2017 · 7 comments
Assignees
Labels

Comments

@benirose
Copy link

benirose commented Jun 9, 2017

I know the cli is not the recommended way to running apostrophe tasks, but since it's a documented feature I thought I would log this issue. I tried to run apostrophe apostrophe-users:add admin admin during my project set up, but got an error. It worked when running node app.js ...

$ apos apostrophe-users:add admin admin
 
 Apostrophe  apostrophe-users:add  Running the task [1/1]
WARNING: No session secret provided, please set the `secret` property of the `session` property of the apostrophe-express module in app.js
Incorrect number of arguments.
 
 Apostrophe  apostrophe-users:add  Failed

$ node app.js apostrophe-users:add admin admin
WARNING: No session secret provided, please set the `secret` property of the `session` property of the apostrophe-express module in app.js
prompt: password:  
@benirose
Copy link
Author

benirose commented Aug 3, 2017

Took another look into this today, and it seems like the cli is not set up to pass arguments to any of the apostrophe commands. I may adjust this and submit a PR.

@benirose
Copy link
Author

benirose commented Aug 3, 2017

It looks like commander doesn't support arguments and options on wildcard commands. We could parse process.argv to get them, not sure if this is something you're interested in supporting or not. Let me know and I can make the change and submit a PR.

@boutell
Copy link
Member

boutell commented Aug 3, 2017 via email

@boutell boutell added the bug label Aug 3, 2017
@abea abea self-assigned this May 19, 2020
@abea
Copy link
Contributor

abea commented Jun 4, 2020

@boutell Given that running core apostrophe tasks is a "nice to have" I suggest we deprecate that feature of the CLI. It could be brought back later, but I'm running across a bug while working on this issue where if I'm resetting a password the text I type in is no longer replaced by ******** if I use apos apostrophe-users:change-password. It does when using node app directly.

The amount of work to get this "nice to have" working property seems outsized to its value.

@boutell
Copy link
Member

boutell commented Jun 5, 2020 via email

@abea
Copy link
Contributor

abea commented Jun 5, 2020

Given that it's a tool and not an application, do you see that as a BC break needing a major version? It might be worth bumping to a major version for the analytics addition anyway (not necessary, but makes some sense).

@boutell
Copy link
Member

boutell commented Jun 5, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants