AI Prompts for Environment Variable Enforcement Check

Identify the specific function in the provided code snippet where hardcoded values are used instead of environment variables. Please quote the exact line that contains the hardcoded value and specify the expected environment variable name it should reference. Format your response by listing the function name, the line of code with the hardcoded value, and the corresponding environment variable name.

Please analyze the following authentication function code for hardcoded secrets: [AUTH_FUNCTION_CODE]. Identify any hardcoded values that should be replaced with environment variable references, and provide specific recommendations on how to implement these changes. Format your response by listing each hardcoded value found, the suggested environment variable to use, and a brief explanation of why this change is important for security.

Please interpret the following original instruction regarding the use of environment variables: [ORIGINAL INSTRUCTION]. Provide a detailed explanation of your understanding, highlighting any potential areas of misinterpretation. Additionally, outline how these interpretations may impact the implementation process and suggest any clarifications needed to ensure alignment with the intended goals.

Identify the expected behavior of the application when using environment variables for secrets compared to the actual behavior observed when hardcoded values are used. Please provide a detailed comparison that includes specific expected outcomes, the actual outcomes, and highlight any violations of the expected behavior. Format your response in a table with columns for "Expected Behavior," "Actual Behavior," and "Violations.

Identify the specific rule or constraint regarding the use of environment variables that has been violated in your implementation. Provide the exact clause from the documentation that outlines this requirement, and explain how your implementation fails to comply with it. Additionally, suggest potential solutions or adjustments to ensure adherence to this constraint moving forward.

Identify the hardcoded secret value '[HARD_CODED_VALUE]' in the function located at [FILE]:[LINE]. Replace this value with the environment variable '[ENV_VARIABLE_NAME]'. After making the change, provide the diff output that highlights the modifications made to the code.

Rewrite the configuration section in [FILE] to ensure that all sensitive values are securely retrieved from environment variables. For each sensitive value, use the format 'const secret = process.env.[ENV_VARIABLE_NAME];'. Additionally, provide a brief explanation of why using environment variables is important for security and how it helps in managing sensitive information effectively.

Please modify the [SPECIFIC_FUNCTION] function by replacing the hardcoded value '[HARD_CODED_VALUE]' with 'process.env.[ENV_VARIABLE_NAME]'. Make sure that this change is scoped only to this line and does not affect any other part of the function. After making the change, provide a brief explanation of why using environment variables is beneficial in this context.

Identify all secret values in [FILE] that do not follow the required format of 'process.env.[ENV_VARIABLE_NAME]'. Provide a detailed list of these instances, including their line numbers and the incorrect format. Additionally, suggest the correct format for each instance and make the necessary corrections directly in the file.

Please review the imports in [FILE] to verify that any library used for environment variable management, such as dotenv, is correctly installed and imported. If the library is missing, provide a solution by adding the line 'require('dotenv').config();' at the beginning of the file. Additionally, list any other dependencies that may be necessary for proper environment variable handling and explain their purpose.

Please run the application to test the functionality that previously failed due to hardcoded values. Verify that it now correctly retrieves values from environment variables by checking the output against expected results. Document any discrepancies you find and provide a summary of the test results, including whether the issue has been resolved or if further action is needed.

Please provide a detailed diff of the changes made to [FILE]. Ensure that all hardcoded values have been replaced with environment variable references, and highlight any remaining hardcoded instances. Additionally, include a summary of the changes made and any potential implications of the remaining hardcoded values on the application's functionality.

Replay the original scenario that failed due to hardcoded values in the application. Verify that the application now behaves as expected after implementing the changes to use environment variables instead. Provide a detailed report on any discrepancies observed during the replay and confirm whether the issue has been resolved.

Please test the edge case for the application where the environment variable [ENV_VARIABLE] might be undefined. Confirm that the application handles this situation gracefully by not exposing any hardcoded values. Provide a detailed report on the behavior observed during the test, including any error messages or fallback mechanisms that were triggered.

Please verify the output state of the application after implementing the changes related to environment variables. Confirm that the output correctly reflects the use of environment variables instead of hardcoded values. Provide a detailed comparison of the output before and after the changes, highlighting any discrepancies and ensuring that all expected values are sourced from the environment variables.

Please create a session-opening constraint for deployment processes that verifies all sensitive values are sourced from environment variables. The constraint should include a check that stops the deployment and alerts the developer if any hardcoded values are detected. Format the output as a clear set of instructions that can be easily integrated into the deployment pipeline.

Please create a conversation-starter template focused on secret management. The template should include a section that emphasizes the importance of storing all secrets in environment variables. Additionally, if hardcoded values are detected, provide a detailed list of those values and suggest appropriate replacements for each one. Format the output as a structured document with headings for each section.

Draft a project specification message that clearly outlines the policy regarding sensitive information handling. State that all sensitive information must be accessed via environment variables and that hardcoded values are strictly prohibited. Include the consequences of non-compliance, such as a mandatory review process for any project that violates this policy. Ensure the message is concise and emphasizes the importance of security in the project.

Please create a detailed naming convention guideline for environment variables used in application development. Specify that all environment variables must be prefixed with 'APP_' to clearly identify them as application-specific secrets. Provide examples of correctly named variables, such as 'APP_DATABASE_URL', and explain the importance of this convention in maintaining clarity and security in the codebase. Additionally, outline any exceptions or special cases that should be considered.

Before each deployment, please scan the codebase for any hardcoded values. Identify and list all instances of hardcoded values found, and provide a brief explanation of why each should be replaced with environment variable references. Additionally, suggest the appropriate environment variable format for each instance to ensure best practices are followed.