[Content Bug] Response Week 3 Step 7 - Cosmos DB Config, mention storage of secrets

[lechnerc77]

Leaky secrets

Identify Steps:

• Step 7

Week:

Week 3

Describe the Issue

• Create your Cosmos Databases: Step 4: From a cost perspective it would make sense to use the serverless tier for the exercise. There is also a CosmosDB emulator that can be used for local development (Link). However, the setup is not straightforward and the experience is not great (at least for Node.js based apps.
• Create your Cosmos Databases: Step 7: Consistent writing of VS Code.
• Create your Cosmos Databases: Step 8: it should be mentioned that for security reasons information about keys should be stored in Azure Key Fault or the access should be secured via managed identities (where possible see Link and dedicated description for CosmosDB).
• The main Function: In the code samples I assume that you can replace the let with const.

Proposed Fix

• Create your Cosmos Databases: Mention that there is also a serverless tier or replace the setup with the serverless tiering. In addition mention the option for local development via the emulator for the sake of completeness.
• Create your Cosmos Databases: Step 7: Replace VSCODE with VS Code.
• Create your Cosmos Databases: Step 8: Mention that for security reasons information about keys should be stored in Azure Key Fault or the access should be secured via managed identities (where possible see Link and dedicated description for CosmosDB).
• The main Function: Replace the let with const where possible.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lechnerc77]

@emsesc @ganning127 : Can we add the pinned label to the issues that should be done after the summer session so that they are ignored by the stale bot?