This message was deleted.
# aws
s
This message was deleted.
b
we have a new release of the AWS provider coming shortly which I think fixes this
q
Hmm what might help for your releases could be to add testing to the examples. I will look around at the Pulumi testing articles and see if I can figure out a reasonable way to create a test for this example that could be triggered upon releases
b
we do run tests on our examples repo https://github.com/pulumi/examples/actions
q
But I assume you aren't testing the specific example that is failing for me or otherwise it would have worked
b
q
That makes it look like it would be trivial to add to that test suite. Maybe I will try loading and see if I can find a way to launch a single integration test locally
Took awhile to get setup but when running the tests via vscode I see
Copy code
Running tool: /usr/local/go/bin/go test -timeout 30s -coverprofile=/tmp/vscode-go4oiqru/go-code-cover <http://github.com/pulumi/examples|github.com/pulumi/examples>

ok  	<http://github.com/pulumi/examples|github.com/pulumi/examples>	0.021s	coverage: [no statements] [no tests to run]
If I could get them to run then I could try to create a test for my specific example
Aside from this let me know when I should try testing the scheduled-function again manually. I thought I saw a new aws provider resource or similar released but re-ran the example and it was still stuck. Maybe the artifact wasn't yet pushed to a repository just yet
b
q
well, it worked!