Yes, you’re correct - it depends on the subscription your org purchased, and you can have Ubuntu Pro without Support. You can read more about subscriptions here: Buy Ubuntu Pro | Ubuntu.
1 Like
Hello @yanisa-hs ,
Could you please update the Patch notices section ? The last version is 24.04.9 but we only see up to the version 24.04.5
Best Regards,
Guillaume
1 Like
Thank you! Just updated them. 
1 Like
@yanisa-hs - do you know when we might expect a proper package search in the new version?
1 Like
@jby No, I’m not sure. We don’t have a timeline set for updates to package search, but it is something that’s on our radar
1 Like
Another couple of questions for you @yanisa-hs:
How can I list all clients (instances) with their respective hardware platform (it seems to be named Product identifier)?
And - why is there no export to/download of a CSV file of clients in the new webgui?
1 Like
Yet another question for you @yanisa-hs:
Any documentation on how to use the REST API with the new version?
This seems outdated: https://ubuntu.com/landscape/docs/make-rest-api-requests
Or it seem to not take into consideration if I have an old type URL like:
https://landscape.canonical.com/account/ACCOUNTID
1 Like
It’s now almost 6 months later - and still no package search in the new web gui?
@jby Landscape’s whole package management experience (including package search) is currently going through a large redesign. So, it’ll still be awhile before these changes are available in-application, and it’s not expected in our next interim release (25.10). We don’t have a set timeline for it yet.
But improving package management is currently being worked on by the Landscape team.
2 Likes
I really don’t want to be rude - but how is it that you “release” a new version where the most basic of functionality is missing?
- No package search
- No billing information
- No export
- No documentation of the API (last time I looked)
I’d say it’s not even in beta state yet…
1 Like
Hey!
Thank you for your feedback. I understand your concerns, and I would like to address them.
I will start by saying that we know the new UI still has no parity with the legacy one, and this is the main reason why we haven’t removed the legacy UI. We don’t want to take any functionality away from users, and any workflow which was possible still is. We are working towards parity, and there is progress with each release, but it will take time, as we have limited resources as well as higher priorities than reaching full UI parity. This is why feedback is very important to us, it helps us prioritize what to bring in first, what to redesign, etc. so thanks for chipping in.
Regarding package search and export: we are redesigning and re-engineering these, which is a very large effort. Given our limited resources, we’d rather focus on providing a better new experience sooner, than reaching UI parity with the current features (which have significant issues) and throwing that work away a few months later (which would also mean delaying the development of the redesigned experience). As Yanisa mentioned, we’re on it, and as I mentioned earlier, functionality is still available (via the legacy UI).
Regarding billing information: we stopped offering pay-as-you-go 3 years ago. Since some customers like it, we haven’t taken it away or forced them on a different offering, but we won’t prioritize parity with this section until we remove the legacy UI.
Regarding API documentation: could you be more specific? We have documentation available for 85/102 endpoints in the V2 REST API here, and we will cover all gaps before the end of the year.
Once again, thanks for your feedback, we’re looking into these issues, and these comments help us improve with each release!
2 Likes
I had this problem with the API earlier, haven’t looked at it in quite a while - you might have fixed it: