Skip to content
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

Upstream 5.85.0 #5161

Merged
merged 7 commits into from
Feb 6, 2025
Merged

Upstream 5.85.0 #5161

merged 7 commits into from
Feb 6, 2025

Conversation

corymhall
Copy link
Contributor

@corymhall corymhall commented Feb 4, 2025

@corymhall
Copy link
Contributor Author

corymhall commented Feb 4, 2025

This change is part of the following stack:

Change managed by git-spice.

@corymhall corymhall changed the base branch from master to upgrade-pulumi-terraform-bridge-to-v3.102.0-ci February 4, 2025 19:14
@github-actions github-actions bot force-pushed the upgrade-pulumi-terraform-bridge-to-v3.102.0-ci branch from 3bdc626 to 94c0821 Compare February 4, 2025 19:20
@@ -48,8 +48,8 @@ index 57bf4c7c94..09b4279db3 100644
+ }
+ }
+
+ sp, ok := c.ServicePackages[servicePackageName]
+ if !ok {
+ sp := c.ServicePackage(ctx, servicePackageName)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

c.ServicePackages was changed to a private type with accessor methods.

prov.Resources["aws_guardduty_member_detector_feature"].ComputeID = func(
ctx context.Context, state resource.PropertyMap,
) (resource.ID, error) {
return attrWithSeparator(state, ",", "detectorId", "accountId", "name"), nil
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This resource currently doesn't support import, so I'm not 100% sure this is correct. Based on the Read method it looks like these three are required

https://github.com/hashicorp/terraform-provider-aws/blob/658a64579f91e53276d2a71da00aa43b854d3de7/internal/service/guardduty/member_detector_feature.go?plain=1#L143

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes. The ID allocation is best-effort. Technically new GUID is a valid ID. We've been trying to match ID to import IDs where possible.

@@ -4666,6 +4668,8 @@ compatibility shim in favor of the new "name" field.`)
"aws_ec2_managed_prefix_list": {Tok: awsDataSource(ec2Mod, "getManagedPrefixList")},
"aws_ec2_transit_gateway_route_tables": {Tok: awsDataSource(ec2Mod, "getTransitGatewayRouteTables")},
"aws_ec2_instance_types": {Tok: awsDataSource(ec2Mod, "getInstanceTypes")},
"aws_vpc_ipam": {Tok: awsDataSource(ec2Mod, "getVpcIpam")},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is aws_vpc_*, but everything else we've been putting in aws_ec2 so just following that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which module does it show up in the TF documentation site? Alongside which resources? Can we match that for minimum surprise?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well the problem is that we haven't been matching TF so far. The TF docs site has a separate section for Vpc (which includes a lot more resources that our Vpc docs section) and a separate Vpc IPAM section.

It seems like we've already diverged pretty far from what the TF docs do, but that also might be because they are able to re-organize the resources on the docs site when they want to.

Screenshot 2025-02-05 at 10 15 05 AM

Also, it might be a moot point because I didn't realize we already had a aws_vpc_ipam resource that we put under the ec2 module so I think we need to also put the datasource there as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to maybe clean this up. WDYT? Aliasing may have our back but would like to move these resources into their new home module that matches TF upstream. Perhaps we can take a task into V7 planning to finish this up?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good idea, we should think about how to reorganize these resources for V7. I'll create an issue to track.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@corymhall corymhall changed the base branch from upgrade-pulumi-terraform-bridge-to-v3.102.0-ci to upgrade-pulumi-terraform-bridge-to-v3.102.0 February 4, 2025 20:14
@corymhall corymhall force-pushed the corymhall/upstream-585 branch from 8aea02c to d03c0dd Compare February 4, 2025 20:14
@corymhall corymhall marked this pull request as ready for review February 4, 2025 21:01
@corymhall corymhall requested a review from a team February 4, 2025 21:01
@corymhall corymhall force-pushed the corymhall/upstream-585 branch from d03c0dd to 09b8261 Compare February 5, 2025 15:13
lambda.WithEndpointResolverV2(newEndpointResolverV2()),
withBaseEndpoint(config[names.AttrEndpoint].(string)),
withExtraOptions(ctx, p, config),
+ p.pulumiCustomizeLambdaRetries(cfg),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anything special going on here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like they added the withExtraOptions thing in there so I just fixed the rebase to add our customization after.

Copy link
Member

@t0yv0 t0yv0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PATCH changes LGTM. Let me know if need a hand fighting CI.

Copy link

github-actions bot commented Feb 5, 2025

Does the PR have any schema changes?

Found 2 breaking changes:

Resources

  • 🟢 "aws:ec2/vpcEndpoint:VpcEndpoint": required: "serviceName" property is no longer Required

Types

  • 🟢 "aws:ec2/getLaunchTemplateNetworkInterface:getLaunchTemplateNetworkInterface": required: "connectionTrackingSpecifications" property has changed to Required

New resources:

  • guardduty/memberDetectorFeature.MemberDetectorFeature
  • route53domains/domain.Domain
  • timestreamquery/scheduledQuery.ScheduledQuery
  • vpclattice/resourceConfiguration.ResourceConfiguration
  • vpclattice/serviceNetworkResourceAssociation.ServiceNetworkResourceAssociation

New functions:

  • ec2/getVpcIpam.getVpcIpam
  • ec2/getVpcIpams.getVpcIpams

Maintainer note: consult the runbook for dealing with any breaking changes.

Copy link

codecov bot commented Feb 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.54%. Comparing base (585aec0) to head (c35cb24).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5161      +/-   ##
==========================================
+ Coverage   24.47%   24.54%   +0.06%     
==========================================
  Files         361      362       +1     
  Lines      144065   144734     +669     
==========================================
+ Hits        35260    35524     +264     
- Misses     108707   109112     +405     
  Partials       98       98              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Base automatically changed from upgrade-pulumi-terraform-bridge-to-v3.102.0 to master February 5, 2025 17:38
@corymhall corymhall force-pushed the corymhall/upstream-585 branch from 7b54123 to b96354c Compare February 5, 2025 17:39
@corymhall corymhall merged commit 10b9d3f into master Feb 6, 2025
25 checks passed
@corymhall corymhall deleted the corymhall/upstream-585 branch February 6, 2025 16:41
@pulumi-bot
Copy link
Contributor

This PR has been shipped in release v6.68.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants