"Operator Cockpit" FAQs
What are the consequences if there exists an unwanted "
manifest.yml" file within the appbinary?
For example, if
manifest.ymlfile exists inside application.war/WEB-INF in appbinary, then the application might be automatically removed from the operator's CF space and cannot be used anymore.
Can the "
routes" attribute be used in conjuction with "manifest" attributes?
routes" attribute should not be used in conjunction with
no-hostname. If used in conjuction, an error will result.
Can I push an application without specifying any
routerelated CLI options or app "manifest" flags?
No. It is always recommended to push an application by specifying
routerelated options. If the
routeis not specified, then the CF CLI attempts to generate a route based on the app name which might cause collisions. You can also use
random-routeattribute to generate a unique
routename and avoid collisions.
What are the pre-conditions to have "Auto deployment" as an available option for deployment?
For auto deployment to be enabled, the following conditions must be satisfied:
Make sure that your application contains the
Validation of the following parameters in the
Auto deployment option
buildpackis not available
pathis not available
memoryis not available
domainparameter is deprecated)
domainsparameter is deprecated)
hostparameter is deprecated)
hostsparameter is deprecated)
random-routeis not available or set to false
For more information on the development files that disable auto deployment, refer Preparation Checklist.
Can we use fixed "
route" in app
It is not recommended to use fixed "
route" since it might cause route collisions following which auto-deployment will fail.
In such cases, you need to use manual deployment with an unoccupied
routeor change the
routeconfiguration as "
Can I use any random format for
No. Operator Cockpit does not support
manifestof random formats. For correct format of
manifest, see the below table:
Implication (when failed)
(If buildpacks parameter is used while uploading from Developer Cockpit, then key will be removed from the manifest file after it is handed over to Operator Cockpit.)
key-value pair(key being String, and value being Object)
Does auto-deployment in Operator Cockpit support
buildpacksparameter in the
manifestfile of an application to provide information regarding the framework and runtime support for an application?
No. Auto-deployment does not support
manifestfile. However, the application can be deployed by following the steps below:
Download the application from Operator Cockpit
buildpacks" parameter in the
Use manual deployment (Deployment via CF CLI) option in Operator Cockpit to deploy the application
manifeststart with slash (/)?
No. If the
manifeststarts with slash(/), then auto-deployment of an application will not work as desired. For auto-deployment to be successful, remove the slash(/) from
manifestand re-start the process.