busy-soccer-65968
06/12/2020, 5:29 PMenough-kite-69616
06/12/2020, 6:04 PMenough-kite-69616
06/12/2020, 6:05 PMimportant-appointment-55126
06/12/2020, 9:55 PMrich-napkin-40911
06/13/2020, 12:03 AMelegant-dress-88912
06/13/2020, 2:21 AM$ pulumi up
...
Diagnostics:
pulumi:providers:gcp (default_2_1_1):
error: no resource plugin 'gcp-v2.1.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v2.1.1`
Version number comes from plugin random
- I can prove this by upgrading it:
$ yarn add @pulumi/random@2.1.2
$ pulumi up
...
Diagnostics:
pulumi:providers:gcp (default_2_1_2):
error: no resource plugin 'gcp-v2.1.2' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v2.1.2`
elegant-dress-88912
06/13/2020, 2:22 AMelegant-dress-88912
06/13/2020, 2:23 AMelegant-dress-88912
06/13/2020, 2:26 AMelegant-dress-88912
06/13/2020, 2:32 AMelegant-dress-88912
06/13/2020, 2:34 AMelegant-dress-88912
06/13/2020, 2:56 AMpulumi stack export > stack.json
2. manually add CRD into stack.json
3. import state back with pulumi stack import --file stack.json
4. refresh resource state with pulumi refresh -t 'urn:...'
- this is to prevent replacement of CRD
5. sync with regular pulumi up
but this is rather tedious and I think it'll be useful to have some pulumi subcommand for this.bitter-australia-87528
06/13/2020, 4:32 AMorange-fountain-17148
06/13/2020, 10:23 AMbored-finland-61499
06/13/2020, 3:54 PMcold-motherboard-287
06/13/2020, 4:23 PMmysterious-pilot-36551
06/14/2020, 12:38 AMdepends_on
option supposed to delay the creation of a resource until the resource it depends on finishes being created? I have a Kubernetes custom resource that depends on a Chart, however, Pulumi is trying to create both the Chart and the custom resource at the same time. This causes it to fail because the CRD isn’t created until the Chart finishes getting created.
Here is an excerpt. Chart is declared on line 26 and the custom resource on line 46.mysterious-pilot-36551
06/14/2020, 12:44 AMnumerous-lifeguard-13411
06/14/2020, 2:09 AMnumerous-lifeguard-13411
06/14/2020, 2:10 AMaws:ec2:SecurityGroup (appserver):
error: 1 error occurred:
* creating urn:pulumi:dev::cisco-exercise::aws:ec2/securityGroup:SecurityGroup::appserver: Error authorizing security group ingress rules: InvalidGroupId.Malformed: Invalid id: "bastion-05865a3" (expecting "sg-...")
numerous-lifeguard-13411
06/14/2020, 2:10 AMnumerous-lifeguard-13411
06/14/2020, 2:31 AMaws:ec2:SecurityGroup (sg-bastion):
error: Error creating Security Group: InvalidParameterValue: Value (sg-bastion-1f46895) for parameter GroupName is invalid. Group names may not be in the format sg-*.
numerous-lifeguard-13411
06/14/2020, 2:31 AMnumerous-lifeguard-13411
06/14/2020, 3:18 AMtags: { Name: "sg_blah" }
is requiredlittle-garage-43399
06/14/2020, 11:12 AMfrom pxglb import *
pxglb is a file with classes I have built. This import is worked fine, until I have added to pxflb file a new class, a "ResourceProvider" class
[1:05 PM] class PXNS1RecordProvider(ResourceProvider):
In this case I get the following error:
error: Exception calling application: No module named 'pxglb'
If I copy paste the classes code into the "main" file (instead of the import), it works fine.
Pulumi version: 2.4.0
Python version: 3.7.7famous-sugar-52038
06/14/2020, 4:51 PMnumerous-lifeguard-13411
06/14/2020, 5:29 PMnumerous-lifeguard-13411
06/14/2020, 11:09 PMpulumi up
again. But that seems pretty grossly manual.numerous-lifeguard-13411
06/14/2020, 11:09 PMaverage-receptionist-65239
06/14/2020, 11:55 PMpulumi up
command is "Waiting for app ReplicaSet be marked available (0/1 Pods available)". However, the deployment is ready. The pod is operating just fine.average-receptionist-65239
06/14/2020, 11:55 PMpulumi up
command is "Waiting for app ReplicaSet be marked available (0/1 Pods available)". However, the deployment is ready. The pod is operating just fine.[1/2] Waiting for app ReplicaSet be marked available (0/1 Pods available)
error: 2 errors occurred:
* the Kubernetes API server reported that "default/search-indexer" failed to fully initialize or become live: 'search-indexer' timed out waiting to be Ready
* Minimum number of Pods to consider the application live was not attained
kubectl
and did a pulumi up --refresh
to work around the issue.