https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
a
Sorry if this was supposed to be in the typescript channel.
l
You won't need to use apply unless you're trying to get at those values immediately. Most of the time, values from other stacks are used in constructors of Pulumi resources, which handle Outputs correctly.
You don't need to cast on these lines, unless there's something about the way you're using the values that requires this. Can you post (as text please, not a picture) how you're using these stack references?
a
I needed to concat the two Secret arays together, after reading the docs, I figured out, I think the proper way to do it. If I do not cast them, TS errors saying type mismatch.
Copy code
const secrets: pulumi.Output<aws.ecs.Secret[]> = await pulumi
    .all([baseSecretArns, envSecretArns])
    .apply(async ([base, env]) => {
      return base.concat(env);
    });
Thank you for replying @little-cartoon-10569
l
You don't need the async in the formal definition of the anonymous function. And you shouldn't await this.
This should do the same thing:
Copy code
const secrets = pulumi
    .all([baseSecretArns, envSecretArns])
    .apply(([base, env]) => [...base, ...env]);
If you need to do this often, it would be more efficient to do it in the exporting stack.
a
That is not valid syntax, base and env do not have iterators on them (Type 'Output<Secret[]>' must have a '[Symbol.iterator]()' method that returns an iterator.), but I have removed the await and async, but even with that, because I have .all returns, I would still need the as on the const variables. This just seems really bad. Let me rethink this to see if there is a way I can do both, I think there may be a way to combine them on this side so I don't have to do all the crazy stuff. That might fix my as concern as well.
I really appreciate you reaching out though.
l
Why are base and env still outputs? They're inside the apply...
a
THis is good stuff!
They end up being this type: pulumi.UnwrappedArray<aws.ecs.Secret>
l
That should have an iterator? If not, then the .concat() optoion is fine too.
a
I don't think I am going to need it, I don't think base and env need to be seperate, ❤️ thank you! Good idea putting it on the export side.
👍 1
l
You can export all 3 sets of secrets for convenience.
6 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by