aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorge Kelly <george.kelly1097@gmail.com>2023-02-07 17:10:22 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-02-09 10:00:13 +0000
commit5daecc25a59ce5bf6c31f5085e6caa7cb543517e (patch)
treed5ddf57757e386e70bff8c1832ab181c77127b32
parent195750f2ca355e29d51219c58ecb2c1d83692717 (diff)
downloadbitbake-contrib-5daecc25a59ce5bf6c31f5085e6caa7cb543517e.tar.gz
fetch2: Add NODE_EXTRA_CA_CERTS to export list
If you are behind a corporate proxy, the npm fetcher uses the proxy IP address already passed in the list of exports. However, it will error if the proxy injects its own root CA certificate. Thus, the NODE_EXTRA_CA_CERTS environment variable must be passed so the user can include their company's root CA as a trusted CA inside node's certificate store. Signed-off-by: George Kelly <george.kelly1097@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
-rw-r--r--lib/bb/fetch2/__init__.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/bb/fetch2/__init__.py b/lib/bb/fetch2/__init__.py
index 5a7a6024d..747356dfa 100644
--- a/lib/bb/fetch2/__init__.py
+++ b/lib/bb/fetch2/__init__.py
@@ -851,6 +851,7 @@ FETCH_EXPORT_VARS = ['HOME', 'PATH',
'DBUS_SESSION_BUS_ADDRESS',
'P4CONFIG',
'SSL_CERT_FILE',
+ 'NODE_EXTRA_CA_CERTS',
'AWS_PROFILE',
'AWS_ACCESS_KEY_ID',
'AWS_SECRET_ACCESS_KEY',