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

so for a directory with ~500 files, it's about 10 minutes

i think it's because of the design. `aws sync` is just a splat, whereas for each object in Pulumi we have to upload, store the result of that update in the state/checkpoint, which is going to have an impact

some users have switched to a dynamic provider to manage objects instead

is there an example of the dynamic provider approach?

<https://github.com/sevenwestmedia-labs/pulumi-components/tree/main/libs/throw-files-in-s3>

knew you were gonna ask so went looking :smile:

Or what I was hoping was to seed the state with sync and then do an import of the objects with refresh so it could handle deltas from that point.

the caveat here is that it won't manage the objects on delete, it has no delete in the crud

i'm not sure if you could seed the state with sync, you'd have to import every object into the state which is going to take just as long I suspect :disappointed: