-
Notifications
You must be signed in to change notification settings - Fork 34
Adding back the build-secret
to the e2e test.
#232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The decision to remove it was a mistake. It was confused with `imageRepoSecret`. The build arg is supposed to be available to the `build` Dockerfile at `/run/secrets/build-secret/filename`. Signed-off-by: Yoni Bettan <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ybettan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/cc @qbarrand |
FYI @enriquebelarte |
/lgtm |
…kubernetes-sigs#350) The decision to remove it was a mistake. It was confused with `imageRepoSecret`. The build arg is supposed to be available to the `build` Dockerfile at `/run/secrets/build-secret/filename`. Signed-off-by: Yoni Bettan <[email protected]> Signed-off-by: Yoni Bettan <[email protected]>
The decision to remove it was a mistake. It was confused with
imageRepoSecret
.The build arg is supposed to be available to the
build
Dockerfile at/run/secrets/build-secret/filename
.Signed-off-by: Yoni Bettan [email protected]