RDS certificates support

[bquintas]

When trying to deploy this in a container service on AWS I can never establish a connection to RDS PG, due to missing certificates, I tried passing PEM files as env variables using CERTIFICATE_AUTHORITIES and CERTIFICATE_AUTHORITIES_BASE64 but always get missing files error.
I've noticed that the current version of the script uses v4.30.14 of cf build pack which only contains a single PEM amazon-rds-ca.pem while the newer versions include the regional pems and apparently also error handling.
Are you planning to bump the cf version soon or do you have a recommendation for how to add the right certs in the build?

[zlogic]

@bquintas The default branch is a legacy branch - unfortunately, some users set up pipelines to always pull the default branch, and we cannot update the default branch without breaking those pipelines.

The latest branch (or a tagged version) uses the latest cf-buildpack.

[mattmarich-wrstbnd]

Can we please get a new tagged version soon including the latest cf-mendix-buildpack (or >= v5.0.13 where the aws certs were added)? We've been on v5.0.4 for 8 months so I feel we're due for an update. docker-mendix-buildpack v5.0.4 uses cf-mendix-buildpack v5.0.9 which doesn't have the latest aws cert additions. In addition to the aws certs, it would also be nice to select a newer version of openjdk, I'm assuming the community would really like if ya'll bumped to using cf-mendix-buildpack:v5.0.15 (which added openjdk 17 and 21 support).

I can't speak for other teams but we really can't rely on running the latest branch in our pipelines so fingers crossed for a new tagged release!