[oc new-build] is there a way to copy mutiple directories using oc new-build with source-image-path flag

[der-ali]

when writing a build config in openshift, i can copy multiple
directories from one container to another like this

source:
    images:
      - from:
          kind: ImageStreamTag
          name: 'buildervscv:latest'
        paths:
          - destinationDir: .
            sourcePath: /opt/app-root/src/dist/.
          - destinationDir: .
            sourcePath: /opt/app-root/src/openshift/conf/.

how can i do the same thing using oc new-build ?

I tried

oc new-build --source-image=builder
--source-image-path=/opt/app-root/src/dist/.:.
--source-image-path=/opt/app-root/src/openshift/conf/.:.
--image-stream=openshift/nginx

oc new-build  --source-image=builder --source-image-path
/opt/app-root/src/dist/.:.  /opt/app-root/src/openshift/conf/.:.
--image-stream=openshift/nginx

oc new-build  --source-image=builder
--source-image-path=[/opt/app-root/src/dist/.:. ,
/opt/app-root/src/openshift/conf/.:.] --image-stream=openshift/nginx

with the fist one only one directory is being copied! and the rest are
throwing an error.
The documentation is only mentioning --source-image-path='': Specify the file or directory to copy from the source image and its destination in the build directory. Format: [source]:[destination-dir]

[adambkaplan]

It seems oc new-build is only using the first value if --source-image-path is set multiple times. You can add additional paths to the BuildConfig once it has been created via oc edit bc <build-name>

fyi @openshift/sig-developer-experience @bparees

[der-ali]

@adambkaplan i used oc patch to add the second sourcePath instead of oc edit because i am using a gitlab pipeline to deploy.

oc patch buildconfig $APP --type=json -p='[{"op":"add","path":"/spec/source/images/0/paths/1","value":{"destinationDir":".","sourcePath":"/opt/app-root/src/openshift/."}}]

it will be though much cleaner to have this done in one command :)

[der-ali]

any news if this feature gonna be implemented?

[adambkaplan]

We have no immediate plans to add this feature, but are more than happy to review a PR.

I'd recommend waiting a bit, since origin is currently being refactored so that oc (and other okd binaries) are hosted in their own repositories.

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