How can secure properties be hidden on CloudHub runtime manager?

Secure properties are crucial for maintaining the confidentiality of sensitive information, such as passwords and API keys, when deploying applications on CloudHub. The correct approach to hide these properties effectively is to store them in the mule-artifact.json file. This file allows you to define a secure properties placeholder for your application, ensuring that sensitive data is not hard-coded or exposed directly within the application source code.

By using the secure properties feature, you can reference these properties in your application without exposing their actual values in logs or other outputs. The mule-artifact.json configuration enhances security by segregating sensitive information from the application logic and provides a standardized way to manage these properties across various environments.

Storing secure properties directly in the runtime configuration, while a possible method, may not provide the same level of abstraction or protection as leveraging the built-in features of mule-artifact.json. Encrypting properties individually could add complexity and may not align with best practices for managing configuration across Mule applications. Additionally, storing properties in a separate database, although secure, introduces unnecessary complexity and might affect the application's performance and deployment workflow.