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
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
boundless-analyst-51913
06/08/2021, 4:53 PMHi, I have a inline program that creates a Table and an API resource from pulumi-cloud, and when I run it the first time (creating the resources) I get this error:
failed to register new resource my-api-resource-name [aws:apigateway/stage:Stage]: Resource monitor is terminating
at Object.registerResource (/node_modules/@pulumi/pulumi/runtime/resource.js:219:27)
at new Resource (/node_modules/@pulumi/pulumi/resource.js:215:24)
at new CustomResource (/node_modules/@pulumi/pulumi/resource.js:307:9)
at new Stage (/node_modules/@pulumi/apigateway/stage.ts:200:9)
at new API (/node_modules/@pulumi/apigateway/api.ts:571:22)
at new HttpDeployment (/node_modules/@pulumi/api.ts:200:20)
at API.publish (/node_modules/@pulumi/api.ts:131:27)
at Resource.output (own code, line points to this codeWhen I run it again, it successfully creates that missing resource. I tried to debug it but I can't find out what the issue could be. Any hints on where to look or how to debug would be very appreciated.)return { url: api.publish().url };
I added some more information to the message.
After further debugging it looks like the issue comes from the fact that there are more than one copy of the Pulumi package that are being used. My app is divided into 2 modules: a CLI and a stand alone library. The CLI depends and uses the library and both have "@pulumi/pulumi" as a dependency, so every package is using its own version of the Pulumi package in its own 'node_modules' folder. Making the pulumi packages to peer dependencies in the library fixed the issue.
Is this an expected behaviour?