You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have one for archiving channels, we need to add one for permanently deleting from the database.
Proposed changes:
rename existing CLI command platform channel delete to platform channel archive to reflect what it does (delete the channel from UI but leave it in the database).
create a new CLI command platform channel delete which permanently deletes a channel from the database (we have one for users and teams)
Channels can be specified by {team}:{channel} using the team and channel names or IDs.
jasonblais
changed the title
[Help Wanted] [PLT-4843] Add CLI tools for archiving channels
[Help Wanted] [PLT-4843] Add CLI tool for deleting channels
May 16, 2017
If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please join our "Developers" community channel.
New contributors please see our Developer's Guide, specifically for machine setup and for developer workflow.
Notes: Jira ticket
We have one for archiving channels, we need to add one for permanently deleting from the database.
Proposed changes:
platform channel delete
toplatform channel archive
to reflect what it does (delete the channel from UI but leave it in the database).platform channel delete
which permanently deletes a channel from the database (we have one for users and teams)Channels can be specified by {team}:{channel} using the team and channel names or IDs.
Format:
platform channel delete {channels}
Example:
sudo ./platform channel delete myteam:mychannel
See related doc for archiving a channel from the CLI: https://docs.mattermost.com/administration/command-line-tools.html#platform-channel-delete
See a PR that added a CLI command for searching for users: #5918
The text was updated successfully, but these errors were encountered: