broad-dog-22463
04/08/2020, 10:53 AMbroad-dog-22463
04/08/2020, 10:53 AMhandsome-cat-98152
04/08/2020, 11:00 AMbroad-dog-22463
04/08/2020, 11:01 AMbroad-dog-22463
04/08/2020, 11:01 AMbroad-dog-22463
04/08/2020, 11:01 AMhandsome-cat-98152
04/08/2020, 11:02 AMbroad-dog-22463
04/08/2020, 11:03 AMbroad-dog-22463
04/08/2020, 11:07 AMbroad-dog-22463
04/08/2020, 11:10 AMbroad-dog-22463
04/08/2020, 11:11 AMbroad-dog-22463
04/08/2020, 11:11 AMbroad-dog-22463
04/08/2020, 11:11 AMbroad-dog-22463
04/08/2020, 11:11 AMbroad-dog-22463
04/08/2020, 11:11 AMhandsome-cat-98152
04/08/2020, 11:15 AM{x: string, y: string}
and create it as {x: 'hello', y: 'world', additionalSecretOutputs: ['y']}
the output of y
would be 'secret' ?broad-dog-22463
04/08/2020, 11:20 AMbroad-dog-22463
04/08/2020, 11:21 AMstale-knife-36790
04/08/2020, 12:43 PMbrave-angle-33257
04/08/2020, 3:01 PMpolite-portugal-60022
04/08/2020, 3:22 PM# Note, I'm abstracting a lot of what we do with simple wrapper classes since 99% of our instances will follow the same patterns. The second reason is to easily load/write templates automagically from provided inputs to script(s)
for resource_objs in template_objs:
# Build all non-disk/non-instance objects first in case there are dependencies later
objs = list( filter( lambda obj: not 'disk' in obj[1].lower() and not 'instance' in obj[1].lower(), resource_objs) )
for obj in objs:
obj[0].build()
# Extract and build all "disk" objects
disk_objs = list( filter( lambda obj: 'disk' in obj[1].lower(), resource_objs) )
for disk_obj in disk_objs:
disk_obj[0].build()
# Extract instance object
instance_obj = list( filter( lambda obj: 'instance' in obj[1].lower(), resource_objs) ).pop()
# Some kind of bug?, need to filter out pulumi.output.Output objects from attached_disks attr
# else, will try to add ALL previously created disks. Not just the disks created in this iteration!!!
instance_obj[0].attached_disks = list( filter(lambda disk: not isinstance(disk, pulumi.output.Output),
instance_obj[0].attached_disks) )
# Append disks to be attached_disks attr and build instance
for disk_obj in disk_objs:
instance_obj[0].attached_disks.append( { 'device_name': disk_obj[0].result.name,
'source': disk_obj[0].result.name } )
instance_obj[0].build()
cool-egg-852
04/08/2020, 3:59 PMelegant-crayon-4967
04/08/2020, 5:18 PMflaky-baker-91034
04/08/2020, 5:32 PMbillions-glass-17089
04/08/2020, 6:08 PMbright-orange-69401
04/09/2020, 8:04 AMdelete_before_replace
does not help me here because the two records are 2 separate resources (they are in different stacks)famous-kite-69533
04/09/2020, 1:20 PMopenssl rand -base64 128
brainy-nest-61978
04/09/2020, 2:02 PMgray-yak-9058
04/09/2020, 4:06 PMpulumi up
on the sandbox and preprod stacks, but I want to lock down the prod stack so that only certain users can run pulumi up
. Is this possible?
2. How does the Pulumi GitHub action work when it comes to multiple stacks? Does it cycle through all stacks within a project? I would like to be able to control when a pulumi up
is run on a specific stack during CI/CD. While making infrastructure changes, I would obviously want to try it in the sandbox or preprod environments before making changes in production. Is this capable with the Pulumi GitHub action or do I need to look for another solution?future-kite-91191
04/09/2020, 4:52 PMPulumi.<stack-name>.yaml
files for each stack. But how can I specify default values that apply to all stacks? Can I specify config data at project level and the Pulumi.<stack-name>.yaml
can override it? Some settings are the same for all stacks most of the time, would be handy to keep it DRY. Is that possible?