Internal Developer Onboarding Tooling Provisioner Script

Role: Principal Infrastructure & Developer Operations Automation Engineer.

Context

• Target workstation operating environment: {{target_os_platform}}
• Mandatory development utilities and runtimes: {{required_cli_tools}}
• Identity and enterprise single sign-on mechanism: {{internal_auth_provider}}
• Engineering role clearance and permission scope: {{access_tier_level}}
• Baseline source repositories to synchronize: {{repo_clone_list}}
• Notifications channel for status logging: {{slack_webhook_channel}}

Task

Author an idempotent workstation setup and developer environment provisioning script that automates package installation, configures authentication tokens, clones necessary codebase dependencies, and validates system readiness for new engineering hires.

Method

1. Detect host system compatibility against {{target_os_platform}} and verify non-root user context.
2. Validate workstation network access and reachability of {{internal_auth_provider}}.
3. Install and lock version numbers for software specified in {{required_cli_tools}}.
4. Initialize credential helpers and role scopes corresponding to {{access_tier_level}}.
5. Sequentially clone and configure upstream remotes for repositories defined in {{repo_clone_list}}.
6. Run post-installation health checks on local runtimes and environment paths.
7. Transmit an execution summary payload containing success metrics to {{slack_webhook_channel}}.

Constraints

• MUST be fully idempotent so repeated runs do not corrupt existing dotfiles or tools.
• MUST NOT hardcode any secrets, tokens, or personal identifiers within the script.
• Gracefully capture failures and provide descriptive troubleshooting messages on stdout.
• Keep total execution time under 10 minutes by skipping already-satisfied dependencies.

Output format

Deliver the response formatted in these exact sections:

1. Shell Script: Production-ready provisioning script with inline comments, function definitions, and traps.
2. Pre-flight Checklist: Markdown table listing prerequisites, required environment variables, and fallback steps.

Self-review

• Verify idempotency across all package management and cloning functions.
• Confirm {{required_cli_tools}} and {{target_os_platform}} are directly utilized in setup logic.
• Ensure secrets handling leverages secure environment variables rather than local disk storage.