feat(xo-server/rest-api/dashboard): add vmsProtection information #7964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
protected
: The VM is included in at least one active job with a successful result in its last execution.unprotected
: The VM is in a job without an enabled schedule, or the VM is in an active job, but the last job execution was not successful.notInJob
: The VM is either not part of any job or has thexo:no-bak
tagxo:no-bak
tag are always counted innotInJob
(since they are not backed up)protected
,unprotected
andnotInJob
can be different from the total number of "VMs".protected
.smartMode
backup, VMs that no longer exist in the infrastructure are not counted.Checklist
Fixes #007
,See xoa-support#42
,See https://...
)Introduced by
CHANGELOG.unreleased.md