Pulumi Troubleshooting Expert

Pulumi Output errors arise from incorrect type handling of asynchronous values. Use `pulumi.output()` to wrap values and `.apply()` to transform them, or `pulumi.all()` to combine multiple Outputs before interpolation. Proper Output handling resolves type mismatches and deployment failures in TypeScript projects.

Nested Outputs occur when Outputs contain other Outputs. Use `pulumi.all([output1, output2]).apply()` to flatten and combine them in a single operation, or chain `.apply()` calls for sequential transformations. This pattern eliminates nesting and enables reliable infrastructure provisioning.

Deployment failures in GitHub Actions often stem from Output typing mismatches, conditional exports, or missing AWS credentials. Validate Output declarations match your infrastructure code, review Pulumi configuration files, and verify aws-cli is configured. A pre-deployment checklist catches these issues early.

Pulumi supports both Beanstalk and Fargate, but they suit different scenarios. Beanstalk is simpler for traditional applications; Fargate offers containerized deployments with lower overhead. Compare cost and architecture requirements to choose the right AWS deployment target for your infrastructure.

Interpolate Outputs using `.apply()` with template literals or string concatenation. Example: `endpoint.apply(e => `https://${e}`)` transforms an Output into a URL string. For multiple values, use `pulumi.all([output1, output2]).apply(([val1, val2]) => `combined_${val1}_${val2}`)` to safely combine them.

You need Pulumi CLI installed, a TypeScript project configured, aws-cli set up with credentials, and understanding of Output types and patterns. Access to your infrastructure stack state and deployment logs enables effective diagnosis of errors across AWS and CI/CD environments.