Enhancement: Add support for specifying a datastore to PBS widget

[choehn86]

Proposed change

Implements changes to accommodate this feature request.

PBS datastore configuration:

Example services.yaml specifying 'local-backups' datastore:

- Proxmox Backup Server:
    href: https://pbs.domain
    description: Proxmox Backup Server
    widget:
      type: proxmoxbackupserver
      url: https://pbs.domain
      username: homepage@pbs!api
      password: apikey
      datastore: "local-backups"

Result:

Example services.yaml without datastore key:

- Proxmox Backup Server:
    href: https://pbs.domain
    description: Proxmox Backup Server
    widget:
      type: proxmoxbackupserver
      url: https://pbs.domain
      username: homepage@pbs!api
      password: apikey

Result is the combination of all datastores used / total:

Type of change

• New service widget
• Bug fix (non-breaking change which fixes an issue)
• New feature or enhancement (non-breaking change which adds functionality)
• Documentation only
• Other (please explain)

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature / enhancement and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

[shamoon]

There are 2 votes on that FR, you and the other user. Let's make sure theres a bit more interest before reviewing this. We can readdress in the future, thanks

[choehn86]

@shamoon Is it worth taking a second look from a bug-fix perspective? Today anyone using the widget who has >1 datastore will get inconsistent monitoring due to the widget being hard-coded to always look at the first entry in the result set, while the PBS API doesn't explicitly return the datastores in a particular order.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.