cmd.Flags().StringVar(&stepConfig.APIEndpoint,"apiEndpoint",`https://api.cf.eu10.hana.ondemand.com`,"Cloud Foundry API endpoint")
cmd.Flags().StringVar(&stepConfig.AppName,"appName",os.Getenv("PIPER_appName"),"Defines the name of the application to be deployed to the Cloud Foundry space")
cmd.Flags().StringVar(&stepConfig.ArtifactVersion,"artifactVersion",os.Getenv("PIPER_artifactVersion"),"The artifact version, used for influx reporting")
cmd.Flags().StringVar(&stepConfig.CfHome,"cfHome",os.Getenv("PIPER_cfHome"),"The cf home folder used by the cf cli. If not provided the default assumed by the cf cli is used.")
cmd.Flags().StringVar(&stepConfig.CfNativeDeployParameters,"cfNativeDeployParameters",os.Getenv("PIPER_cfNativeDeployParameters"),"Additional parameters passed to cf native deployment command")
cmd.Flags().StringVar(&stepConfig.CfPluginHome,"cfPluginHome",os.Getenv("PIPER_cfPluginHome"),"The cf plugin home folder used by the cf cli. If not provided the default assumed by the cf cli is used.")
cmd.Flags().StringVar(&stepConfig.DeployDockerImage,"deployDockerImage",os.Getenv("PIPER_deployDockerImage"),"Docker image deployments are supported (via manifest file in general)[https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#docker]. If no manifest is used, this parameter defines the image to be deployed. The specified name of the image is passed to the `--docker-image` parameter of the cf CLI and must adhere it's naming pattern (e.g. REPO/IMAGE:TAG). See (cf CLI documentation)[https://docs.cloudfoundry.org/devguide/deploy-apps/push-docker.html] for details. Note: The used Docker registry must be visible for the targeted Cloud Foundry instance.")
cmd.Flags().StringVar(&stepConfig.DeployTool,"deployTool",os.Getenv("PIPER_deployTool"),"Defines the tool which should be used for deployment.")
cmd.Flags().StringVar(&stepConfig.BuildTool,"buildTool",os.Getenv("PIPER_buildTool"),"Defines the tool which is used for building the artifact. If provided, `deployTool` is automatically derived from it. For MTA projects, `deployTool` defaults to `mtaDeployPlugin`. For other projects `cf_native` will be used.")
cmd.Flags().StringVar(&stepConfig.DeployType,"deployType",`standard`,"Defines the type of deployment, either `standard` deployment which results in a system downtime or a zero-downtime `blue-green` deployment.If 'cf_native' as deployType and 'blue-green' as deployTool is used in combination, your manifest.yaml may only contain one application. If this application has the option 'no-route' active the deployType will be changed to 'standard'.")
cmd.Flags().StringVar(&stepConfig.DockerPassword,"dockerPassword",os.Getenv("PIPER_dockerPassword"),"If the specified image in `deployDockerImage` is contained in a Docker registry, which requires authorization, this defines the password to be used.")
cmd.Flags().StringVar(&stepConfig.DockerUsername,"dockerUsername",os.Getenv("PIPER_dockerUsername"),"If the specified image in `deployDockerImage` is contained in a Docker registry, which requires authorization, this defines the username to be used.")
cmd.Flags().BoolVar(&stepConfig.KeepOldInstance,"keepOldInstance",false,"In case of a `blue-green` deployment the old instance will be deleted by default. If this option is set to true the old instance will remain stopped in the Cloud Foundry space.")
cmd.Flags().StringVar(&stepConfig.LoginParameters,"loginParameters",os.Getenv("PIPER_loginParameters"),"Addition command line options for cf login command. No escaping/quoting is performed. Not recommended for productive environments.")
cmd.Flags().StringVar(&stepConfig.Manifest,"manifest",os.Getenv("PIPER_manifest"),"Defines the manifest to be used for deployment to Cloud Foundry.")
cmd.Flags().StringSliceVar(&stepConfig.ManifestVariables,"manifestVariables",[]string{},"Defines a list of variables as key-value Map objects used for variable substitution within the file given by manifest. Defaults to an empty list, if not specified otherwise. This can be used to set variables like it is provided by 'cf push --var key=value'. The order of the maps of variables given in the list is relevant in case there are conflicting variable names and value between maps contained within the list. In case of conflicts, the last specified map in the list will win. Though each map entry in the list can contain more than one key-value pair for variable substitution, it is recommended to stick to one entry per map, and rather declare more maps within the list. The reason is that if a map in the list contains more than one key-value entry, and the entries are conflicting, the conflict resolution behavior is undefined (since map entries have no sequence). Note: variables defined via 'manifestVariables' always win over conflicting variables defined via any file given by 'manifestVariablesFiles' - no matter what is declared before. This is the same behavior as can be observed when using 'cf push --var' in combination with 'cf push --vars-file'.")
cmd.Flags().StringSliceVar(&stepConfig.ManifestVariablesFiles,"manifestVariablesFiles",[]string{`manifest-variables.yml`},"path(s) of the Yaml file(s) containing the variable values to use as a replacement in the manifest file. The order of the files is relevant in case there are conflicting variable names and values within variable files. In such a case, the values of the last file win.")
cmd.Flags().StringVar(&stepConfig.MtaDeployParameters,"mtaDeployParameters",`-f`,"Additional parameters passed to mta deployment command")
cmd.Flags().StringVar(&stepConfig.MtaExtensionDescriptor,"mtaExtensionDescriptor",os.Getenv("PIPER_mtaExtensionDescriptor"),"Defines additional extension descriptor file for deployment with the mtaDeployPlugin")
cmd.Flags().StringVar(&stepConfig.MtaPath,"mtaPath",os.Getenv("PIPER_mtaPath"),"Defines the path to *.mtar for deployment with the mtaDeployPlugin")
cmd.Flags().StringVar(&stepConfig.SmokeTestScript,"smokeTestScript",`blueGreenCheckScript.sh`,"Allows to specify a script which performs a check during blue-green deployment. The script gets the FQDN as parameter and returns `exit code 0` in case check returned `smokeTestStatusCode`. More details can be found [here](https://github.com/bluemixgaragelondon/cf-blue-green-deploy#how-to-use). Currently this option is only considered for deployTool `cf_native`.")
cmd.Flags().IntVar(&stepConfig.SmokeTestStatusCode,"smokeTestStatusCode",200,"Expected status code returned by the check.")
