Andreas Lindhé

Document `$patch: delete`

5

### Eschewed features - [X] This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature. ### What would you like...

Allow operator to set PSA in Rancher

3

## Change description In Rancher, it is not enough to have `patch` permissions for a namespace in order to set PSA labels. It is also required to have the `updatepsa`...

Set namespace in commands in chart notes

1

## Change description This change explicitly sets the namespace in the commands suggested in the chart's NOTES.txt file, which are rendered upon installation. Before this change, the namespace was not...

The Trident operator fails to install via Helm on Rancher

8

**Describe the bug** When installing the Trident operator from the Helm chart in a Kubernetes cluster managed by Rancher, the operator fails because it is unable to add the PSA...

Document TridentBackendConfig custom resource

5

**Describe the solution you'd like** The TridentBackendConfig custom resource is undocumented when inspecting it with `kubectl explain`: ```console $ kubectl explain TridentBackendConfig KIND: TridentBackendConfig VERSION: trident.netapp.io/v1 DESCRIPTION: ``` Having documentation...

Trident operator doesn't clean up during uninstall

2

**Describe the bug** After uninstalling the Trident operator (using Helm), I find that there are multiple CR and CRDs left. This is pretty annoying since the lingering resources still have...

**Describe the bug** There exists duplicate entries for the `namespace` resource in the `trident-operator` ClusterRole: https://github.com/NetApp/trident/blob/ee2d9743551c82635d411da878389ffbd9f5f655/helm/trident-operator/templates/clusterrole.yaml#L10-L16 https://github.com/NetApp/trident/blob/ee2d9743551c82635d411da878389ffbd9f5f655/helm/trident-operator/templates/clusterrole.yaml#L244-L250 This makes it harder than necessary to review what permissions are granted to...

Redundant UI: Checkboxes and Toggles

8

I'm really confused by the UI when calling the service. There's both checkboxes and toggle switches available for some of the options. Is that a bug? 

The generated report is in fact named `watchman_report.txt`, not `thewatchman_report.txt`. https://github.com/dummylabs/thewatchman/blob/23298faaec5bb1ca21f28124844e86b6b3cbf9fa/custom_components/watchman/const.py#L8

It seems the 'read_file' and 'write_file' functions are defined but never used. ```console $ git grep -e 'read_file' -e 'write_file' custom_components/watchman/utils.py:async def read_file(hass: HomeAssistant, path: str) -> Any: custom_components/watchman/utils.py:async def...