No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Screen Shot 2021-10-21 at 3.46.29 pm.png

anyone got any idea what might be going on here :-
I set the region, i check the region , try to import a resource i know exists in the region i have set, the import fails because pulumi says the bucket is not in a different region to what i have set . . . :shrug:

I’m not sure `import` uses the config and I’m wondering if it’s getting some underlying region setting.

nope …..
```04:52:36 bmeehan@_ip-10-232-33-223:~/repos/itplat-pulumi-infrastructure/src/aws/s3$ env | grep AWS
07:59:52 bmeehan@_ip-10-232-33-223:~/repos/itplat-pulumi-infrastructure/src/aws/s3$ ```

yeah so im really keen to get some info on how to set the region properly for a `pulumi import` as i have tried setting in pulumi config and setting by env var, both fail

im guessing it is this flag on import which seems just horrible
```      --provider string                       The name and URN of the provider to use for the import in the format name=urn, where name is the variable name for the provider resource```

so i thought that meant something like
```pulumi import --yes -s ipd-aws-s3 aws:s3/bucket:Bucket itplat-regional-629205377521-us-west-1 itplat-regional-629205377521-us-west-1 --provider us-west-1=urn:pulumi:ipd-aws-s3::aws_iam::pulumi:providers:aws::us-west-1
...
ok yes that seems to work```
very hard to read help description