![]() ![]() When creating a new project with an invalid raml zip, Studio does not copy those files to the workspace.ĪPI Custom Policy Editing is a beta feature. It shows them as modified and not as eliminated. The workaround is to use different workspaces for each environment so that there will no be problem with users authentication.įolder decorators are not being shown correctly when users eliminate them. When changing API Platform environments from production to another environment, Studio would try to update offline projects, showing connection error marker. The workaround is to delete the corrupt domain project and right click in the imported project → Mule → Associate with API Gateway domain, until the project is generated correctly displaying, for example, "api-gateway_2_0_3 : api-gateway". When importing a zipped project related to the API Gateway’s default domain (for example, proxies generated from API Platform), if the domain project does not exist in the workspace already, there is a chance that it will be generated incorrectly, resulting in an entry in the Package Explorer like "api-gateway_2_0_3 : ". Object Store support gaps around Idempotent Redelivery Policy, Aggregators and DevKit token manageĬreate JSON metadata from example does not support Big Integers ![]() RecordVars and record payload should be editable in a commit block. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |