Description of problem:

Cloud Foundry handles the web process type with some backward compatibility in manifest files. Specifically, the configuration for the web process can be placed at the top level of the application configuration in the manifest, rather than explicitly listed under a processes array with type: web. The web process is a special and required process type for all applications and can be implicitly defined without explicitly defining the type: web at application level.

For example, while you could define a web process with details like disk quota, health checks, instances, memory, log rate limit, and timeout directly under the application in the manifest, it is generally recommended to use the processes block for individual process configurations, especially for clarity and when defining multiple process types.

To express the same single-process application example using a processes block, you would move the process-specific configurations from the top-level application configuration into a dedicated processes array, with a type: web entry. This approach is available with Cloud Foundry API (CAPI) V3 and is recommended for clarity, especially if you anticipate adding other process types in the future.

Right now, the discover command only moves an application level process to the processes block from the discovery manifest if there is a a value for the type field at application level, and doesn't take the implicit web process.

Application level defined processes should always be moved to the processes dictionary from the discovery manifest, to make sure it lists all defined processes in the application.

 Version-Release number of selected component (if applicable):

v0.8.0-alpha.4