melodic-policeman-4147412/07/2021, 2:38 PM
These resources are in an unknown state because the Pulumi CLI was interrupted while waiting for changes to these resources to complete. You should confirm whether or not the operations listed completed successfully by checking the state of the appropriate provider. For example, if you are using AWS, you can confirm using the AWS Console. Once you have confirmed the status of the interrupted operations, you can repair your stack using 'pulumi stack export' to export your stack to a file. For each operation that succeeded, remove that operation from the "pending_operations" section of the file. Once this is complete, use 'pulumi stack import' to import the repaired stack.
billowy-army-6859912/07/2021, 2:42 PM
when you originally ran Pulumi?
melodic-policeman-4147412/07/2021, 2:49 PM
billowy-army-6859912/07/2021, 2:51 PM
melodic-policeman-4147412/07/2021, 2:51 PM
billowy-army-6859912/07/2021, 2:54 PM
- it's a safety mechanism to ensure you don't create duplicate/overriding resources. I'd recommend running through it again but waiting till the calls have completed. You should see your outputs resolved and the bucket created like this:
Do you want to perform this update? yes Updating (dev): Type Name Status pulumi:pulumi:Stack quickstart-dev created + └─ gcp:storage:Bucket my-bucket created Outputs: + bucketName: "<gs://my-bucket-62f8bc7>" Resources: + 2 created Duration: 3s
Anyone else successfully using pulumi to manage gcp infra?We have a case study from Sourcegraph about how they use Pulumi on GCP https://www.pulumi.com/case-studies/sourcegraph/
melodic-policeman-4147412/07/2021, 3:07 PM
billowy-army-6859912/07/2021, 3:10 PM