Skip to content

chore : update docker-compose file#405

Draft
StefanoDoc wants to merge 4 commits intomainfrom
chore/fix-docker-compose
Draft

chore : update docker-compose file#405
StefanoDoc wants to merge 4 commits intomainfrom
chore/fix-docker-compose

Conversation

@StefanoDoc
Copy link
Contributor

add emulation command to azure-storage image
change azure-cosmos image to vnext-preview for ARM support

resolve IEL-9

List of Changes

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@changeset-bot
Copy link

changeset-bot bot commented Feb 9, 2026

⚠️ No Changeset found

Latest commit: 7e31480

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added the chore label Feb 9, 2026
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
1 Security Hotspot
9.9% Duplication on New Code (required ≤ 3%)
E Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@@ -0,0 +1,122 @@

process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

Check failure

Code scanning / CodeQL

Disabling certificate validation High

Disabling certificate validation is strongly discouraged.

Copilot Autofix

AI 1 day ago

In general, you should not globally disable TLS certificate validation. Instead, either (a) leave the default verification behavior in place, or (b) if you must trust a custom/self‑signed certificate (for an emulator or internal endpoint), explicitly configure a proper CA/certificate for that connection only, rather than changing NODE_TLS_REJECT_UNAUTHORIZED.

The single best fix here, without changing existing functionality beyond restoring secure defaults, is to remove the line that sets process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";. Cosmos DB client connections will then use standard TLS verification rules, and any other libraries in the process will no longer have their certificate checks disabled globally. No other code in this file appears to rely on this environment variable, and we do not need to add any imports or helper methods to achieve the fix. The change is localized to the very top of setup-cosmos-containers.js, removing line 2.

Suggested changeset 1
setup-cosmos-containers.js

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/setup-cosmos-containers.js b/setup-cosmos-containers.js
--- a/setup-cosmos-containers.js
+++ b/setup-cosmos-containers.js
@@ -1,6 +1,6 @@
 
-process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
 
+
 const { CosmosClient } = require("@azure/cosmos");
 
 const endpoint = process.env.COSMOS_ENDPOINT || "http://cosmos-db:8081";
EOF
@@ -1,6 +1,6 @@

process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";


const { CosmosClient } = require("@azure/cosmos");

const endpoint = process.env.COSMOS_ENDPOINT || "http://cosmos-db:8081";
Copilot is powered by AI and may make mistakes. Always verify output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant