When the manifest.json is not correct it shows "Incorrect file type" instead an actual error.

[mahomedalid]

When sync a catalog with an incorrect manifest.json is not correct it shows "Incorrect file type" instead an actual error. We found out the issue was that we cannot have a default with value and required: true in the parameters, there was a lot of trial/error on catalog sync to figure it out.

Example param:

  - id: location
    name: 'Location'
    description: 'Region location'
    type: string
    default: 'eastus'
    required: true

[ericaguthan]

Hi @mahomedalid, thanks for reaching out!

There is work currently in progress that will make errors like this more specific and easier to debug.

[mahomedalid]

Thank you @ericaguthan ! We also had a few other instances with confusing errors, instead of creating a issue we can maybe just report them here. For example, when an environment fails to be created it shows something like: "Provisioned state failed", without any specifics about why. Of course, sometimes we can go to the deployments and see the error, but sometimes it is something related to the parameters or something else, that does not show up because the deployment has not been created.