Origin: How to pass separate template files to oc process?

Created on 8 Oct 2018 · 9Comments · Source: openshift/origin

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

componencli kinfeature lifecyclrotten prioritP3

Source

lomholdt

👍1

Most helpful comment

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

soltysh on 8 Oct 2018

👍2 🎉1

All 9 comments

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

soltysh on 8 Oct 2018

👍2 🎉1

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 on 6 Jan 2019

/remove-lifecycle stale

lomholdt on 7 Jan 2019

Issues go stale after 90d of inactivity.

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

/lifecycle stale

openshift-bot on 7 Apr 2019

/remove-lifecycle stale

lomholdt on 7 Apr 2019

Issues go stale after 90d of inactivity.

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

/lifecycle stale

openshift-bot on 12 Jul 2019

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 on 12 Aug 2019

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-bot on 11 Sep 2019

@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.