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 you want to keep the old versions there as well as uploading the new ones?

I'm also having troubles making beanstalk to accept new version from pulumi

So the idea of Pulumi is that it describes what your end-state should be. So if you want multiple versions available, you're going to have to loop through your local directory and create multiple `BucketObject` resources

The same with the beanstalk. It'll create the new version and then delete the old one

so I guess that another solution is to write a function that uploads file to S3 and tells pulumi to take S3 key when changing `ApplicationVersion` object which should trigger environment version change as well