1. Add the command  parameters to the spec  field of the DeploymentConfig  object. You can also add an args  field, which modifies the command  (or the ENTRYPOINT  if command  does not exist). 

## 3.2.1.6. Viewing deployment logs 

## Procedure 

spec: containers: - name: <container_name > image: 'image' command: - '<command>' args: - '<argument_1>' - '<argument_2>' - '<argument_3>' 

For example, to execute the java  command with the -jar  and /opt/app- root/springboots2idemo.jar  arguments: 

spec: containers: - name: example-spring-boot image: 'image' command: - java args: - '-jar' - /opt/app-root/springboots2idemo.jar 

1. To stream the logs of the latest revision for a given DeploymentConfig  object: 

$ oc logs -f dc/<name> 

If the latest revision is running or failed, the command returns the logs of the process that is responsible for deploying your pods. If it is successful, it returns the logs from a pod of your application. 

2. You can also view logs from older failed deployment processes, if and only if these processes (old replication controllers and their deployer pods) exist and have not been pruned or deleted manually: 

## 3.2.1.7. Deployment triggers 

$ oc logs --version=1 dc/<name> 

A DeploymentConfig  object can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster. 

