Author: Anil Bawne
- Application properties are variables that act as placeholders in the Mule application
- It is set in Mule runtime at runtime.
- When you deploy an application, or update an existing application in the Runtime Manager console, the Mule runtime engine supplies the values for the property variables using information you configure in the Runtime Manager console’s Properties tab.
Steps to create safely hidden application properties
- Inside the Mule application’s mule-artifact.json file, list the property names you wish to safely hide under the secureProperties key as a comma-separated array.
- Deploy application to cloudHub.
- Enter your application properties as you normally would.
- Click Apply Changes.
Steps to change credentials at runtime
- Go to runtime manager
- Go to Application
- Select your application
- Go to setting -> properties
- Change required credentials.
- Click Apply Changes
Before changing access Key
Change accessKey, secretKey
After changing accessKey, secretKey
- If you look at the Runtime Manager you will notice that the value of properties is hidden/masked and there is no way one can retrieve this value.
- CloudHub maintains the security flag for those properties.
- When we update the credentials, it will restart the application automatically.
- Moving the application from one environment to another, safely hidden application properties will not get copied to the new environment.
Whenever we re-deploy same/updated application previously set properties in runtime will be available and used by application