This message was deleted.
# awss
sparse-intern-71089
10/09/2023, 4:59 PMThis message was deleted.
b
billowy-army-68599
10/09/2023, 6:14 PM
This isn’t how Pulumi works and is highly irregular. Can you provide more information about what happened here? Ideally, full step by step details about what you did
b
blue-translator-21668
10/09/2023, 6:17 PMI agree, I’m extremely confused by it.
So I originally had a project deploying an S3 bucket and some other “baseline” resources to an account. I think abstracted the resources out to a separate project so I could deploy them to multiple accounts. When I ran the new project and expected the resources for the account that already had the resources deployed to it to fail, but it succeeded and has the bucket (and other resources) in it’s state
blue-translator-21668
10/09/2023, 6:17 PMI even tried to create a second stack off of the original project to see if I could force it to fail and got the same results
b
billowy-army-68599
10/09/2023, 6:18 PM
How are you defining the bucket?
billowy-army-68599
10/09/2023, 6:18 PM
What are the buckets that you defined called?
billowy-army-68599
10/09/2023, 6:18 PM
(Ie: how do you they appear in the API/console)
b
blue-translator-21668
10/09/2023, 6:20 PMI’m using the basic plulumi class-aws provider and creating them blank so far.
They are all called the same name, which is why I expected it to fail.
In pulumi cloud, the bucket is clearly in every state, but they all link to the exact same bucket in AWS.
blue-translator-21668
10/09/2023, 6:23 PMI tried to update my aws provider to the latest version to check that off, and see the same results
blue-translator-21668
10/09/2023, 6:25 PMwoah even if I use the awscli to try and create the same bucket it “works”
blue-translator-21668
10/09/2023, 6:25 PMand I don’t get the usual 400 error
blue-translator-21668
10/09/2023, 6:42 PMI am reaching out to AWS support cause it seems to be on the AWS side.
b
billowy-army-68599
10/09/2023, 6:44 PM
Can you please show the code you’re using? I suspect you’re running into autonaming. The resource name in pulumi is not the name the resource gets given in the api, we append some uniqueness to the resource to prevent collisions
b
blue-translator-21668
10/09/2023, 6:44 PMhaha I promise I’m not 😆
blue-translator-21668
10/09/2023, 6:44 PMWhen I try to create the same bucket using the awscli I get the same behavior
blue-translator-21668
10/09/2023, 6:45 PMaws is acting like it’s creating it even though it already exists
b
billowy-army-68599
10/09/2023, 6:46 PM
🤯
b
blue-translator-21668
10/09/2023, 6:46 PMit’s blowing my mind
b
billowy-army-68599
10/09/2023, 6:46 PM
Wow, let me know how that turns out. I’ve never see. Anything like it before
b
blue-translator-21668
10/09/2023, 7:26 PM@billowy-army-68599 so I learned something new today. Apparently in us-east-1 s3 will still return a 200 if you own the bucket for “legacy compatibility” so idk how that should be handled in pulumi 😂
l
little-cartoon-10569
10/09/2023, 7:28 PMDoes this not happen outside of us-east-1?
b
blue-translator-21668
10/09/2023, 7:28 PMit does not
blue-translator-21668
10/09/2023, 7:29 PMblue-translator-21668
10/09/2023, 7:29 PMsee
BucketAlreadyOwnedByYoul
little-cartoon-10569
10/09/2023, 7:29 PMSuddenly I feel like a teenage girl. In as much as I'M TELLING EVERYONE I EVER MET, right now.
b
blue-translator-21668
10/09/2023, 7:32 PMI feel like I’m in the twilight zone. I can’t have been the first to run into this. I guess to fix it in pulumi/terraform you would just check to see if the bucket exists before you try to create it.
l
little-cartoon-10569
10/09/2023, 7:33 PMMy recommendation is to recognize that everything in us-east-1 crashes x10 as much as in any other region, and accordingly to never use it.
little-cartoon-10569
10/09/2023, 7:33 PMWe have to rely on it for IAM, billing and more, so reduce the load there and use other regions.
b
blue-translator-21668
10/09/2023, 7:35 PMtrue. If I was around when the infrastructure was originally provisioned I would’ve recommended that 🙃
🤗 1
blue-translator-21668
10/09/2023, 7:38 PMI don’t see any issues logged before in pulumi but it seems like it could be pretty rough if you aren’t aware of that. I wonder if there could be an input specifically for this case.
blue-translator-21668
10/09/2023, 7:39 PMI did find a terraform issue on it https://github.com/hashicorp/terraform-provider-aws/issues/13587
blue-translator-21668
10/09/2023, 7:39 PMI wonder if that behavior wasn’t bridged to pulumi
blue-translator-21668
10/09/2023, 7:39 PMit was merged July 2022
l
little-cartoon-10569
10/09/2023, 7:42 PMI like this:
I accidently used the same bucket name in two Terraform workspaces, and Terraform didn't throw any errors. The two workspaces ended up overwriting each other's KMS key settings on the bucket, which caused lots of issues.That's like saying "I encrypted the payroll file and destroyed the key. My staff didn't approve". Understatement much?
b
blue-translator-21668
10/09/2023, 7:43 PM“10/10 would not recommend”
l
little-cartoon-10569
10/09/2023, 7:44 PMAh damn I can't see the changelog for v4.24.. is that do to with Hashicorp's fun relicensing experiment?
little-cartoon-10569
10/09/2023, 7:44 PMNmind it worked, something is just slow
b
blue-translator-21668
10/09/2023, 7:45 PMI don’t think their providers are under the new license. I believe they are all open still
l
little-cartoon-10569
10/09/2023, 7:50 PMConfirmed that the correct Terraform code is in the upstream submodule.
little-cartoon-10569
10/09/2023, 7:53 PMIt looks like pulumi-aws v5.13 or newer is required. Can you confirm you have that?
b
billowy-army-68599
10/09/2023, 7:53 PM
@blue-translator-21668 can you open an issue so we can track this?
b
blue-translator-21668
10/09/2023, 7:53 PM@billowy-army-68599 for sure
@little-cartoon-10569 yeah, I had 5.40 before and then upgraded to 6.X when troubleshooting
👍 1
blue-translator-21668
10/09/2023, 8:01 PM