-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(ci): Changed the process of token getting. From docker arguments … #5131
fix(ci): Changed the process of token getting. From docker arguments … #5131
Conversation
…to docker secrets
❌ Deploy Preview for dev-web-novu failed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me! 🔥
maybe before merging these changes to next
we can try the full deployment to the dev env? and we can also verify that the images that are built include the bullmq-pro
package in the node_modules
.
This is a very good idea Pawel. I'll do as you say |
Just as a small note, it's not really a huge issues since the ee dockers are in the private repository. But I totally agree that it's a better practice |
…ty-bugfix' into inf-184-docker-enterprise-security-bugfix
What change does this PR introduce?
Docker containers always try to build enterprise version. Here it was suggested to use double quotes instead of single so it actually works as intended. But if we change single quotes to double quotes the variable BULL_MQ_PRO_NPM_TOKEN will be visible every time during a docker build process. Even if we try to hide it the Docker build best practice doesn't recommend to use arguments and environment variables for secret values. Anyone can take a look at this values using "docker image history" ot "docker inspect"
Why was this change needed?