provider-upgrade-analysis

# Provider Upgrade Analysis

## Overview

Analyze the impact of upgrading Terraform providers or modules before making changes. Identify breaking changes, deprecations, and required code modifications.

**Announce at start:** "I'm using the provider-upgrade-analysis skill to assess this upgrade."

## Process

### Step 1: Identify Current State

```bash
# Current Terraform version
terraform version

# Current provider versions
terraform providers

# Lock file details
cat .terraform.lock.hcl
```

### Step 2: Identify Target Version

Determine what version to upgrade to:
- Latest stable
- Specific version requested
- Next major/minor version

### Step 3: Research Breaking Changes

For each provider/module upgrade:

#### AWS Provider Example

```bash
# Check CHANGELOG
# https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md

# Check UPGRADE guide for major versions
# https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-5-upgrade
```

#### Key Sources

| Provider | Changelog Location | Upgrade Guide |
|----------|-------------------|---------------|
| AWS | GitHub CHANGELOG.md | /docs/guides/version-X-upgrade |
| Azure | GitHub CHANGELOG.md | /docs/guides/X.0-upgrade-guide |
| Google | GitHub CHANGELOG.md | /docs/guides/version_X_upgrade |

### Step 4: Analyze Impact

#### Breaking Changes Categories

| Category | Impact | Example |
|----------|--------|---------|
| **Removed Resources** | HIGH | Resource type no longer exists |
| **Removed Arguments** | HIGH | Required attribute removed |
| **Changed Defaults** | MEDIUM | Default value changed |
| **Renamed Resources** | MEDIUM | Resource renamed, state migration needed |
| **New Required Args** | MEDIUM | New required argument added |
| **Deprecations** | LOW | Will be removed in future |

#### Code Scan

Search for affected resources/attributes:
```bash
# Find usage of deprecated resource
grep -r "aws_deprecated_resource" --include="*.tf"

# Find usage of removed argumen