Context
As clients begin the process of migrating content into Arc, they often add "junk" or test content to help further development. These pieces of test content may be things like a "kitchen sink" article for front-end developers, or items POSTed in before the adapter is fully complete. While it's useful to have these things in the API at the beginning of a project, it is not useful to have them in the API long-term and can lead to confusing results when trying to determine the source of some bugs.
Request
This feature idea is an ability within the Arc APIs/Core Services that would allow a user to completely nuke all content in that API instance based on the content type (story, image, video, etc). Obviously, access to this ability would need to be heavily protected/restricted, in order to prevent someone from accidentally deleting all of the content in production.
Guest
Yes please.
I think the feature is a good idea but not as an api endpoint. Maybe a button in arc admin heavily guarded by permissions and are you sure dialogs
Can we get this for all the apps like site service too