hashicorp/terraform-provider-aws

aws_transfer_server::identity_provider_type causes replacement

Open

#46,229 opened on Jan 30, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (10,310 forks)github user discovery
enhancementgood first issueservice/transfer

Repository metrics

Stars
 (11,045 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

This is more of a bug than an enhancement but the bug template did not fit either.

AWS Transfer Family now supports changing identity_provider_type without replacement (announced Oct 24, 2025: https://aws.amazon.com/about-aws/whats-new/2025/10/aws-transfer-family-changing-idp-type/).

The Terraform provider still has ForceNew: true on this attribute at internal/service/transfer/server.go:L155, forcing unnecessary server recreation.

Proposal:

Remove ForceNew: true from identity_provider_type to allow in-place updates:

 "identity_provider_type": {
     Type:             schema.TypeString,
     Optional:         true,
-    ForceNew:         true,
     Default:          awstypes.IdentityProviderTypeServiceManaged,
     ValidateDiagFunc: enum.Validate[awstypes.IdentityProviderType](),
 },

### Affected Resource(s) or Data Source(s)

aws_transfer_server::identity_provider_type causes replacement

### Potential Terraform Configuration

```hcl

References

Would you like to implement the enhancement?

No

Contributor guide

Research direction
Review the `identity provider type` schema in `internal/service/transfer/server.go`, understand how `ForceNew` determines resource replacement, then update the code and add a test to confirm that changing this attribute triggers an update rather than a recreation.
Tech stack
awsgo
Domain
cloudinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoTerraform
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75