cold-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.rhythmic-tailor-27305
06/15/2020, 7:47 AMrhythmic-tailor-27305
06/15/2020, 7:48 AMvictorious-gigabyte-4729
06/15/2020, 5:56 PMnumerous-lifeguard-13411
06/15/2020, 6:45 PMsalmon-needle-46218
06/15/2020, 6:49 PMpulumi/actions
docker container?miniature-petabyte-40567
06/15/2020, 7:19 PMAccessLogs = new Aws.LB.Inputs.LoadBalancerAccessLogsArgs
{
Bucket = aws_s3_bucket.Lb_logs.Bucket,
Enabled = true,
Prefix = "test-lb",
},
numerous-lifeguard-13411
06/15/2020, 7:28 PMastonishing-quill-88807
06/15/2020, 7:49 PMexisting_vpc = ec2.get_vpc(tags={'Name': 'my-vpc-name'})
if existing_vpc and existing_vpc.not_in_stack():
import_opts = ResourceOption(import_=existing_vpc.id)
astonishing-quill-88807
06/15/2020, 7:50 PMnot_in_stack
functionality can do some broad lookup of whether Pulumi is already managing the given VPC?white-beard-6027
06/15/2020, 7:52 PMpulumi config set --path "path/of/secret-key/"
and entered a weird looking 16 char pwgen
random password.
And Pulumi detected that it looks like a password and asked me to use --secret
flag to save it securely.
How cool is that! 🙂
Pleasant surprise. And a DX.mysterious-pilot-36551
06/15/2020, 10:38 PMgreat-byte-67992
06/15/2020, 11:39 PMDate.now + N days
that won’t update on every deployment, perhaps only updating when it’s within a week of the expiry date?future-daybreak-2871
06/16/2020, 8:32 AMfuture-daybreak-2871
06/16/2020, 8:33 AMecs_cluster = aws.ecs.Cluster("ecsCluster", name="cluster-name", tags=default_tags)
and trying to refer to it using ecs_cluster.name
(tried ecs_cluster.name.apply(lambda name: name)
too.future-daybreak-2871
06/16/2020, 8:34 AM<pulumi.output.Output object at 0x7f717c021d30>