equinor / radix-platform

Omnia Radix platform - base scripts and code
MIT License
27 stars 3 forks source link

Is it possible to provide build-time secrets? #128

Closed nemzes closed 4 years ago

nemzes commented 5 years ago

From @flyrev:

We need to authenticate with a feed in Azure DevOps as part of the image building process. We are retrieving internal NuGet packages as part of the build process.

In this particular case it is a licensing/IP issue. We are using a library which is neither written nor owned by Equinor. The code itself is not available. We receive the binaries for the library and add them as dependencies. Instead of having the binaries in every repository that needs it, creating a package of it and making it available through a private feed seems like the best way to handle this.

Brynjulf commented 4 years ago

Me and the team I am on would like to see this issue resolved, we have an npm package that is on the internal equinor npm registry.

jgvabo commented 4 years ago

@equinor/omnia-radix - can you provide an update on the status of this issue? Has it been added to the backlog? If so - with what priority? We'd like to move the REP client & client API, but we need to pull some packages from the Equinor internal npm registry, and thus require this functionality

emirgens commented 4 years ago

This is registered in our backlog and placed in the list of prioritised stories. However it is not possible to say when it will be started on/finished.

Our ref: https://equinor.atlassian.net/browse/RA-71

ingeknudsen commented 4 years ago

We have now delivered a feature for defining build secrets on Radix. Please see https://www.radix.equinor.com/docs/reference-radix-config/#build for more info. Let us know if you find any issues with the solution

jgvabo commented 4 years ago

Thanks!