Catalog sync results and troubleshooting logs #12
Description
We found catalog sync a little difficult to troubleshoot, we believe the experience could be improved in different ways, every bullet may be it's own issue maybe we can split this.
- When the catalog sync succeeds using the CLI, the command does not show any information about it, it just returns blank. Using the portal, we get a notification.
- When the catalog does not sync, either in the CLI or Portal, there is some try and error to figure it out the issue.
- There are not logs in the logs workspace (Azure Monitor) to be queried.
- At the end, one of the issues was that we cannot provide a default value and required set to true in any of the manifest parameters. The error was not clear ("Incorrect file type") When the manifest.json is not correct it shows "Incorrect file type" instead an actual error. #13
- When listing the catalog items, would be useful to see/query the manifest version and/or the git hash, so we know if the latest sync was successful or not.
- Adding a catalog item list to the portal (UX). Feature Request | Adding a catalog item list to the portal (UX) #14