This message was deleted.
# typescripts
sparse-intern-71089
09/21/2022, 4:06 PMThis message was deleted.
s
square-hair-965
09/21/2022, 4:07 PMi wonder if pushing infra to the array that will be fed to
pulumi.all({group1, group2}).apply([...groups])l
little-cartoon-10569
09/21/2022, 8:12 PMYou want to output the ASGs.. do you mean, you want to export them as stack exports? You can use ... notation for this, and you don't need
all()apply()little-cartoon-10569
09/21/2022, 8:14 PMIf you mean, you want to use some properties of the ASGs in an
apply()apply()<http://pulumi.info|pulumi.info>.log()s
square-hair-965
09/21/2022, 8:14 PMi guess it might be a little hard to follow, but I'm having difficulty with outputting things that might only exist in certain stacks, like in a primary web region
square-hair-965
09/21/2022, 8:15 PMthings that are conditionally created based on a configuration boolean flag for example
l
little-cartoon-10569
09/21/2022, 8:16 PMI don't know what "outputting" means in this context. If you create something conditionally, what's stopping you from "outputting" it, either conditionally or unconditionally (may be undefined)?
s
square-hair-965
09/21/2022, 8:17 PMright so by outputting I mean exporting resources, so say I conditionally created a cron server in one web region and tried to get that output in another projects stack, that output is actually undefined for this corresponding stack but I wouldn't know that at the time the plan is made
square-hair-965
09/21/2022, 8:18 PMis this just kind of a common problem you run into or is there some way to work around this
square-hair-965
09/21/2022, 8:19 PMwell I would know that, but pulumi does not
l
little-cartoon-10569
09/21/2022, 8:20 PMIf it's just exporting, and you want to export "all the things" without explicitly naming them all, then you can push them into an array and export the array?
little-cartoon-10569
09/21/2022, 8:20 PMThe conditional things won't get pushed in some stacks, the code will continue to work and be correct in all stacks.
s
square-hair-965
09/21/2022, 8:21 PMok that was my intuitive thought as well, i'll run with that idea
square-hair-965
09/21/2022, 8:21 PMthx
l
little-cartoon-10569
09/21/2022, 8:21 PMThat said, you'll find when consuming those exports, that naming and exporting them one at a time will make life easier for the consumer of the stack (usually).
s
square-hair-965
09/21/2022, 8:22 PMyeah that's been my usual process, and what I ended up doing with the first example, but i've gone with array exports for large collections, for instance a collection of sqs queues
l
little-cartoon-10569
09/21/2022, 8:23 PMIf you implement your infra in a spec-first / test-first "fulfill my ultimate requirement and let my stack design evolve", you'll find how you need to access those exports before you create the code that does the exporting. This will save implementation time by designing the correct API before the implementation.
s
square-hair-965
09/21/2022, 8:26 PMright, i'll keep that in mind as the project grows, thx for your help
square-hair-965
09/21/2022, 8:50 PMso yeah just confirmed that this does work:
Copy code
export const metricAlarms = pulumi.all(_metricAlarms).apply(([...alarms]) => alarms.map((alarm) => {
return {
id: alarm.id,
arn: alarm.arn
}
}));👍 1