-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: TestAccBatchJobQueue_MigrateFromPluginSDK failing on v5.66.0 #39320
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Looks like this duplicates #39257 which already is fixed on latest, good news. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This change upgrades upstream to v5.67.0. Fixes #4435 Fixes #4454 **v5.66.0 changes:** Notable upstream additions: New resources: - datazone/environment.Environment New functions: - glue/getRegistry.getRegistry - organizations/....getOrganizationalUnitDescendantOrganizationalUnits - quicksight/getAnalysis.getAnalysis - quicksight/getQuicksightAnalysis.getQuicksightAnalysis Unfortunately the aws_quicksight_analysis datasource cannot yet be fully supported in the provider because excessively large type hierarchies in Quicksight cause issues for Pulumi SDKs. This is the same problem that makes "definition" fields unavailable for Quicksight resources. A solution is being explored in #4449 but in the meantime the "definition" field is not available yet in Pulumi for the given datasource. There also was a regression hashicorp/terraform-provider-aws#39320 in v5.66.0 that tripped pulumi-aws testing so the matching pulumi-aws release is skipped. **v5.67.0 changes:** - cloudformation/stackInstances.StackInstances - codebuild/fleet.Fleet - computeoptimizer/enrollmentStatus.EnrollmentStatus - computeoptimizer/recommendationPreferences.RecommendationPreferences - costoptimizationhub/enrollmentStatus.EnrollmentStatus - costoptimizationhub/preferences.Preferences - datazone/assetType.AssetType - lambda/functionRecursionConfig.FunctionRecursionConfig New functions: - codebuild/getFleet.getFleet Unfortunately one of the upstream features that introduced support for IAM role chaining is projecting as a breaking change to Pulumi types. Since our policy is to prioritize backwards compatibility, this feature has been backed out and is not yet available in the upcoming pulumi-aws release. See: hashicorp/terraform-provider-aws#22728 Reminder opened to track this in #4459
Terraform Core Version
1.8.3
AWS Provider Version
5.66.0
Affected Resource(s)
Expected Behavior
Migrating aws_batch_job_queue instances from V0 schema (SDKv2) to the current schema is no longer working. This is evidenced by the following failing acceptance test:
Note that the test passes on 5.65.0 version of the provider.
It seems to be related to tags handling and I suspect one of these commits triggered the issue, though I have not taken the time to root cause it.
Actual Behavior
See failing test above.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
See failing acc test above.
Steps to Reproduce
See failing acc test above.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: