Miactl issues with visibility, supportedBy properties

[dallas-fletchall]

What product are you having troubles with?

Console

What Console version are you using?

1.112.1

Description

We have 2 separate installations of Mia, prod and non-prod. During the development of github actions while working with our non-prod instance, we opened a discussion, #589 , to get assistance with properties that were causing issues when deploying plugins.

We were able to address the issues based on the provided schema, and were successful in deploying to our non-prod instance.

Now that we are trying to deploy to our production environment, we are seeing errors with items that seem to be supported in the schema. Versions were compared against prod and non-prod (without difference):

Mia-Platform Suite Version: 13.4.0
Console Version: 1.112.1
cms-backend: 5.1.2
v1-adapter: 4.1.6
auth0-client: 3.2.3
oauth-login-site: 7.2.1

We use identical JSON documents in our prod and non-prod instances, and our github action sets the tenantId prior to upload. Our JSON documents get inserted or updated as expected in the non-prod instance, but fail for our production environment when visibility and/or supportedBy properties exist.

Actual Outcome

When documents have visibility defined:

We removed the item and tried from my local machine:

Finally, we removed the supportedBy property for a single plugin to get the desired result for that plugin:

Expected Outcome

We expect to be able to define the visibility and supportedBy fields in the document so that we can automate the process. All items should have been inserted.

Additionally, we would like to configure our prod and non-prod instances to treat plugins the same. Currently, we do not know how to validate what the differences are.

[epessina]

Hi @dallas-fletchall ,

the issue is a permissions one. Some fields (namely visibility, supportedBy, supportedByImage and publishOnMiaDocumentation) can be set only by Company Owners or Project Administrators with the marketplace.manage.root permission. It seems like these conditions are only met on the no-prod installation.

[dallas-fletchall]

Thanks for the quick response, docs cover this. We forgot about this step when applying with our prod SA.

(FWIW, the docs show marketplace.root.manage, just in case someone else stumbles onto this error)

[epessina]

My bad, the correct one is indeed marketplace.root.manage. Thanks for the heads up!