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

Aws s3 bucket conversion has missing unknown property 'transitionDefaultMinimumObjectSize' among [rules bucket expectedBucketOwner]; #254

Closed
brandonpollack23 opened this issue Dec 12, 2024 · 4 comments
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@brandonpollack23
Copy link
Contributor

brandonpollack23 commented Dec 12, 2024

What happened?

when converting https://github.com/terraform-aws-modules/terraform-aws-s3-bucket

PCL conversion works fine but when converting to a language we get

error: could not generate output program: :0,0-0: unknown property 'transitionDefaultMinimumObjectSize' among [rules bucket expectedBucketOwner];

This is meant to be part of BucketLifecycleConfigurationV2

Removing this line in the PCL causes the conversion to go over smoothly.

Example

na

Output of pulumi about

na

Additional context

No response

Contributing

No response

@brandonpollack23 brandonpollack23 added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Dec 12, 2024
@brandonpollack23
Copy link
Contributor Author

Upon investigation, this was added in the upstream provider at commit f6fda8c746d2b6951ae59d7a20d33dbaafe0d70f

It exists in our docs: https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketlifecycleconfigurationv2/#inputs

but when I run pulumi package get-schema aws it is not in there

@brandonpollack23
Copy link
Contributor Author

Closing, updating my provider worked. We should probably do something about this when a user is converting to make sure the versions match even when across pulumiverse versions, at the very least print a message.

@pulumi-bot
Copy link

Cannot close issue:

  • does not have required labels: resolution/

Please fix these problems and try again.

@Frassle
Copy link
Member

Frassle commented Dec 12, 2024

We should probably do something about this when a user is converting to make sure the versions match even when across pulumiverse versions, at the very least print a message.

That's tricky isn't it? I don't think the bridge tells us what version of the TF provider its running against, if that was in the mapping file we could at least warn. If there was some way to inverse map that as well (tf version -> pulumi version) we could just download the right plugin. Something to ask about in ideation today maybe.

@justinvp justinvp added resolution/no-repro This issue wasn't able to be reproduced and removed needs-triage Needs attention from the triage team labels Dec 16, 2024
@justinvp justinvp closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants