package-repositories should be searchable by name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Low
|
Unassigned |
Bug Description
When working with package repositories (actually this is applicable to any object you can work with in MAAS), the only way to read a specific repository is by passing the secret ID:
maas admin package-
where ID is some number starting at 0.
I have no idea what the ID of a repo is. None. I can read them all, then parse the data and determine that at this point, the third repository listed in the MAAS UI has an id of 28, NOT 3.
I dont have issue with using ID as a search key but I should also be able to search/read based on Name matching, which is far more natural.
Thus:
maas admin package-
which would return the data for the repository where the name key matches the string "My Custom PPA".
When I'm writing a script (bash, thus not using the python library), it's much less complex to simply ask for data based on a natural key, rather than having to parse ALL data to match an arbitrary numeric key to a natural identifier like Name.
Same when manually managing maas via the MAAS CLI in general.
summary: |
- package-repositories should be searchable by name + [2.3]package-repositories should be searchable by name |
Changed in maas: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
milestone: | none → next |
Changed in maas: | |
status: | Invalid → Confirmed |
summary: |
- [2.3]package-repositories should be searchable by name + package-repositories should be searchable by name |
Changed in maas: | |
status: | Confirmed → Triaged |
importance: | Wishlist → Low |
milestone: | next → none |
This really isn't an issue with the API. We provide a RESTAPI which should use unique ID's to reference objects.
This is more of an issue with the CLI, which will come when the new CLI is complete.