Print env vars

An Apify actor that outputs all environment variables available during execution. Useful for debugging, verifying configurations, or understanding the runtime context within the Apify platform.

Overview

This actor simply retrieves and prints the complete set of environment variables from process.env and the parsed variables from Actor.getEnv(). It runs with no configuration and provides a snapshot of the runtime environment, which includes Apify-specific details (like IDs, tokens, proxy settings) and system-level information.

Key Features

• Dual Output: Displays both raw environment variables (process.env) and the parsed, Apify-specific environment variables (Actor.getEnv()).
• Zero Configuration: Runs immediately with default settings; no input is required.
• Open Source: The code is publicly available for inspection and modification.
• Developer Tool: Primarily useful for debugging actor runs, checking assigned resource IDs, and confirming environment variable availability.

How to Use

1. Run the Actor: Execute the actor from the Apify Console, via API, or as part of a workflow.
2. View Output: After execution, check the actor's run output. The environment variables will be printed in the log and available in the dataset.
3. No Input Required: The actor functions without any specific input parameters.

Input/Output

Input: This actor does not require or use any input. You can run it with an empty input object {}.

Output: The actor produces a log containing two main JavaScript objects:

1. Raw Environment Variables: The complete process.env object.
   js // Example snippet: { APIFY_ACTOR_RUN_ID: 'isBHoiJgoZxdFGedb', APIFY_PROXY_HOSTNAME: '10.0.83.204', APIFY_TOKEN: '*********', NODE_ENV: 'production', // ... many more }

2. Parsed Environment Variables: The object returned by Actor.getEnv(), which structures Apify-specific variables.
   js // Example snippet: { actorRunId: 'isBHoiJgoZxdFGedb', apiBaseUrl: 'http://10.0.83.204:8010/', dedicatedCpus: 0, memoryMbytes: 256, // ... more }

The exact variables will differ with each run, reflecting the unique context of that execution (e.g., different Run IDs, proxy ports, or memory allocation). Sensitive values like tokens and passwords are automatically masked.