[x] Susbcription triggers - a blocked resource should not trigger
[x] Cron subscriptions - a blocked resource should not launch a job
[x] I want to mention the blocking of resources in the documentation
I went for a pretty good upgrade of the documentation :scroll:
Closes #220
Now possible to block a resource so that it is not used in any subscription, cron or event. It allows for remembering a resource, but not scanning/probing them again.
The PR introduces the "is" filter for resources, where you can specify a boolean. The only supported boolean right now is "blocked. "is: blocked" represents true, "-is: blocked" represents false.
The UI, when blocking a resource, will always confirm with the user that they really want to block/unblock a resource.
I chose to not delete the data of a resource when blocked. It makes more sense to remember what they had, for future reference and for unblocking.
The UI for the 3 types of resources is similar, and only the host's UI will be shown.
By default, the page is filtered by "-is: blocked" to only show items that are not blocked.
You can block in the list resources page:
You can block in the view-resource page:
A blocked resource shows that it is blocked by adding the panel section "Blocked" with the timestamp.
Missing:
Closes #220
Now possible to block a resource so that it is not used in any subscription, cron or event. It allows for remembering a resource, but not scanning/probing them again.
The PR introduces the "is" filter for resources, where you can specify a boolean. The only supported boolean right now is "blocked. "is: blocked" represents true, "-is: blocked" represents false.
The UI, when blocking a resource, will always confirm with the user that they really want to block/unblock a resource.
I chose to not delete the data of a resource when blocked. It makes more sense to remember what they had, for future reference and for unblocking.
By default, the page is filtered by "-is: blocked" to only show items that are not blocked.
You can block in the list resources page:
You can block in the view-resource page:
A blocked resource shows that it is blocked by adding the panel section "Blocked" with the timestamp.