Anypoint CLI docs for DesignCenter - upload project says it creates the project if it doesn't exist, but it is incorrect (https://github.com/mulesoft/anypoint-cli/blob/master/src/commands/designcenter/project.js#L120)

https://github.com/mulesoft/docs-runtime-manager/blob/latest/modules/ROOT/pages/tgw-attach-arm.adoc says:

One transit gateway can support up to 10 VPC attachments.

Where the limitation comes from? Is it a limitation of Anypoint Platform?

https://docs.mulesoft.com/runtime-manager/tgw-about#limitations seems to describe the limitation comes from AWS.

The following values are governed by AWS limits:

• Maximum number of transit gateways per VPC
• Maximum number of VPCs that you can attach to a transit gateway

For information about limitations when attaching a VPC to an AWS transit gateway, see Transit gateway attachments to a VPC in the AWS documentation.

However, attachments per transit gateway is 5000 in the AWS documentation, not 10.
I'm confused.

Please update the first diagram in this document, the diagram directly below the verbiage "The graphic below shows a default Anypoint VPC architecture:"

The bottom path that depicts connecting to mule-worker-internal-.cloudhub.io on ports 8091 and 8092 is incorrect...it should show connections on ports 8081 and 8082 instead...

Remember that ports 8091 and 8092 are only used in the case where dedicated load-balancer is used.

Updating this diagram will help lots of folks better understand what firewall rules are required to allow minimal connectivity in their VPCs and minimize confusion.

Thanks!

The links to the VPC Discovery form 9.5 result in a 404 for customers and internal users.

[https://docs.mulesoft.com/runtime-manager/to-request-vpc-connectivity](Docs page)
[https://docs.mulesoft.com/downloads/runtime-manager/VPC-form-v9.5-template.xlsx] (Missing file)

Under 'Overview' we have the following text:

CPU
This metric is not available on Windows.

The total CPU usage of the server, as a percentage:

CPU usage

System available processing power

System load average

The field "System available processing power" has no metric. Additionally, the current Anypoint Platform interface calls this field "Available Processors". Please clearly define what this field is measuring.

Team,

Could we add more information on the response and if this does work for RTF?

runtime-mgr standalone-application describe

runtime-mgr standalone-application describe [options]
This command describes the standalone application passed in identifier.
This command does not take any options, except for the default ones: --help, -f/--fields and -o/--output.

I am getting the following message when attempting to Replace a Certificate on an Existing Load Balancer

public certificate chain is invalid (the Nth certificate must be signed by Nth+1)

I am following this doc.
https://docs.mulesoft.com/runtime-manager/lb-cert-upload#replace-a-certificate-on-an-existing-load-balancer

When only 1 cert (The Primary Certificate) is included in the public.pem it works but when we add multiple chain such as both The Primary Certificate & The Intermediate Certificate it throw this error. Please attempt to duplicate, it worked for us last time.

The Primary Certificate
-----BEGIN CERTIFICATE-----
(Your Primary SSL certificate: your_domain_name.crt)
-----END CERTIFICATE-----

The Intermediate Certificate
-----BEGIN CERTIFICATE-----
(Your Intermediate certificate: DigiCertCA.crt)
-----END CERTIFICATE-----

As per the JDK Versions of Mule Runtime Deployment Strategies

JDK versions

The version of JDK that CloudHub implements for all apps built with Mule runtime 3.5.1 or later is JDK 1.7. Mule runtime 3.7.0 also supports JDK 1.8. Apps built with runtime 3.5.0 or earlier are deployed with JDK 1.6.

However, under the Additional Information section of the Support Article Java 11 Support in CloudHub Runtimes

Mule Runtime 4.x does support JDK 11, however as of the publishing of this article, all CloudHub and Anypoint Platform Services are deployed on JDK8.

This causes confusion on the actual JDK/JRE for Mule Runtimes 4.x and is further complicated by the Article Mule Runtime support for Java 11 FAQ into consideration.

CloudHub API v2 doesn't have the following endpoint. Coud you update the doc?

https://github.com/mulesoft/docs-runtime-manager/blob/latest/modules/ROOT/pages/deploy-application.adoc

POST https://anypoint.mulesoft.com/cloudhub/api/applications/hello/deploy