Replies: 4 comments
-
CLI is not actively being maintained. That may be the reason @p-try |
Beta Was this translation helpful? Give feedback.
-
The API can replace the CLI, but it would be nice to have the documentation. Maybe dropping the CLI in favor of the API would be simpler and more powerful. Third-party CLIs and libraries will likely be proposed by the community. |
Beta Was this translation helpful? Give feedback.
-
Well... We either get features OR the documentation. Also; as far as I know, CLI is being dropped in favor of API @docjyJ |
Beta Was this translation helpful? Give feedback.
-
Thanks for following up on this so quickly! Alright, I'll check out the API. I'm sure I can find my way around it by looking at the source code for the start until some documentation is available. Dropping a deprecated API in favor of a more powerful and modern API makes sense. But it'd be nice of course if the dropping of one feature had only happened after the replacement feature was sufficiently accessible. |
Beta Was this translation helpful? Give feedback.
-
What happened?
As per the documentation stalwart-cli supports management of domains and other pricipal entities:
https://stalw.art/docs/management/cli/directory/domains
In v0.10.0 this seems to have been intentionally removed:
b59f5f1
I assume this may have been a temporary change and it was not supposed to be shipped. It would be a pity to remove these CLI commands as they are particularily useful whenever Stalwart is used as an e-mail server module of another software project.
How can we reproduce the problem?
Run
stalwart-cli
in a v0.10.0 container:Stalwart Mail Server CLI
Previously available subcommands
domain
,account
,list
andgroup
aren't there anymore.Version
v0.10.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
LDAP
What operating system are you using?
Docker
Relevant log output
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions