Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request juju#18654 from gfouillet/v4/dqlite/resources/wire…
…up/6402-resource-facade juju#18654 > [!WARNING] > Include commits from juju#18634 (which move domain.Resources to core and remove current core.Resources) > > prdesc [x] Wait for merge juju#18634 * Wire up resources facade ListResources to domain * Remove AddPendingResources from the facade code. ## Checklist <!-- If an item is not applicable, use `~strikethrough~`. --> - [X] Code style: imports ordered, good names, simple structure, etc - [X] Comments saying why design decisions were made - [X] Go unit tests, with comments saying what you're testing - [X] [Integration tests](https://github.com/juju/juju/tree/main/tests), with comments saying what you're testing - [X] [doc.go](https://discourse.charmhub.io/t/readme-in-packages/451) added or updated in changed packages ## QA steps ### setup ```sh juju bootstrap lxd lxd juju add-model test juju deploy juju-qa-test qa juju add-unit qa juju deploy juju-qa-test qa1 --resource foo-file=test.txt juju add-unit qa1 juju deploy juju-qa-test qa2 --resource foo-file=1 juju add-unit qa2 ``` ### Test resources command ```sh juju resources qa # Resource Supplied by Revision # foo-file store 2 juju resources qa --details # Unit Resource Revision Expected # qa/0 foo-file - 2 # qa/1 foo-file - 2 juju resources qa1 # Resource Supplied by Revision # foo-file upload 2025-01-20T17:14 # Supplied by might be admin, depending of other PR. juju resources qa1 --details # Unit Resource Revision Expected # qa1/0 foo-file - 2025-01-20T17:142 # qa1/1 foo-file - 2025-01-20T17:14 juju resources qa2 # Resource Supplied by Revision # foo-file store 1 juju resources qa2 --details # Unit Resource Revision Expected # qa2/0 foo-file - 1 # qa2/1 foo-file - 1 ``` > [!NOTE] > It should be possible to test the loading of a resource into a unit, but it is not wired yet. Depends on > prdesc juju#18669 > > However, the QA would be: > ```sh > juju deploy juju-qa-test qa3 > juju resources qa3 --details > # Unit Resource Revision Expected > # qa3/0 foo-file - 2 > juju add-unit qa3 > juju resources qa3 --details > # Unit Resource Revision Expected > # qa2/0 foo-file 2 2 > # qa3/0 foo-file - 2 > ``` > [!NOTE] > It is not possible yet to test the `[Updates Available]` section of the resources report. We need to wire the revision worker first [JUJU\-6401](https://warthogs.atlassian.net/browse/JUJU\-6401) ## Documentation changes None ## Links **Jira card:** [JUJU\-6402](https://warthogs.atlassian.net/browse/JUJU-6402)
- Loading branch information