Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
q
quaint-electrician-41503
10/11/2021, 5:20 PMStill trying to resolve the issue creating scheduled functions via the pulumi example: https://github.com/pulumi/examples/issues/1098 . Can someone take 5 minutes and try to reproduce on the latest pulumi to help determine if it's an issue with my local install / config or a bug?
b
billowy-army-68599
10/11/2021, 5:35 PMwe have a new release of the AWS provider coming shortly which I think fixes this
q
quaint-electrician-41503
10/11/2021, 5:40 PMHmm 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
billowy-army-68599
10/11/2021, 5:43 PMwe do run tests on our examples repo
https://github.com/pulumi/examples/actions
q
quaint-electrician-41503
10/11/2021, 5:51 PMBut I assume you aren't testing the specific example that is failing for me or otherwise it would have worked
b
billowy-army-68599
10/11/2021, 6:16 PMnot at this time it seems, no:
https://github.com/pulumi/examples/blob/master/misc/test/aws_test.go
q
quaint-electrician-41503
10/11/2021, 6:50 PMThat 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
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
billowy-army-68599
10/11/2021, 8:13 PMyep the pipeline is still running https://github.com/pulumi/pulumi-aws/actions/runs/1330252771
q
quaint-electrician-41503
10/12/2021, 8:49 AMwell, it worked!