I saw the doc today and try to use it but my origin was not up to date :p.
I try it once I update Origin (There's a lot of change) but I still have the same issue.
Here are my build config secret part
The "scmsecret" is my secret test key from ssh-key. Is there something that I'm doing wrong?
Le 2 février 2016 à 12:29, Ben Parees <bparees redhat com> a écrit :we've just added a feature which allows you to inject secrets into the build process so they are available during the "assemble" invocation, which sounds like what you need. You'll need to be on the latest origin (the code just dropped in the last week or so), here are the docs:
https://docs.openshift.org/latest/dev_guide/builds.html#using-secretsOnce you setup the build to inject your secret value, you can modify your assemble script to use it when invoking composer.On Tue, Feb 2, 2016 at 3:07 PM, Johary RAVELONJATOVO <johary icloud com> wrote:Hi everyone,
I actually try to deploy a symfony 2 project with OpenShift Origin. The source code of my project is on a private repository and I have create a secret with my ssh key to access on it "private-repo-secret". With that I have no problem to access on the source code with OpenShift Origin.
After that I create a STI custom image, which detects if there's a composer.json on the project and if so it launched "composer install" command.
I made some test and it works. It detects the composer.json and after that it launches the "composer install" command.
The problem is when it did the "composer install", it's correct with public dependencies but not with private. I got an issue with ssh key because it needs the "private-repo-secrets" during the build with "composer install"
users mailing list
users lists openshift redhat com
--Ben Parees | OpenShift