How to pass separate template files to oc process?

[lomholdt]

When I oc process -f template.yaml I would like to split my different objects into several files such as service.yaml, route.yaml, deploymentconfig.yaml. Basically I should be able to do something like oc process -f service.yaml -f route.yaml This is how Kubernetes does it. But when I do it with oc process I get only one of the templates outputted. Is this not possible in oc?

Version

oc v3.6.173.0.83
kubernetes v1.6.1+5115d708d7
features: Basic-Auth

Server https://openshift
openshift v3.7.64
kubernetes v1.7.6+a08f5eeb62

Steps To Reproduce

oc process -f deploymentconfig.yaml -f service.yaml

Current Result

Only one of the resources is outputted

Expected Result

A complete list of the resources inputted

Additional Information

N/A

[soltysh]

It's not a bug, that's how this was originally written, though I agree we should allow multiple, changing to enhancement.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[lomholdt]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[lomholdt]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[the-zucc]

Just bumping this, this would be very useful. Something like a -R flag could be useful, for example for processing multiple templates at once and using the same param-file

[soltysh]

@adambkaplan fyi

[adambkaplan]

cc @dperaza4dustbit

[mhtgrwl5]

/reopen

[openshift-ci]

@mhtgrwl5: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.