discloud.config resource allocation and plan tier compatibility

Resource Management in discloud.config

Discloud utilizes a discloud.config file to define application parameters, including the main entry point and versioning. While the platform manages resource limits based on the user's specific plan tier, the configuration file primarily focuses on application metadata rather than explicit resource requests.

When transitioning an application between different plan tiers, it is unclear if the platform dynamically adjusts the container's RAM and CPU allocation based on the account level or if specific flags within the configuration file are required to signal a change in resource requirements.

Does the platform automatically scale the container resources to the maximum allowed by the current plan upon redeployment? If not, what is the documented method for requesting a specific resource limit within the discloud.config file?