This message was deleted.
# generals
sparse-intern-71089
10/27/2023, 5:14 PMThis message was deleted.
d
dry-keyboard-94795
10/27/2023, 5:52 PMIf the UserPool is part of the current stack, what's preventing you from using the resource directly?
s
silly-apple-46154
10/27/2023, 5:52 PMcircular dependency...
d
dry-keyboard-94795
10/27/2023, 5:57 PMHmm, you could split your resources between multiple files and do imports, or maybe use promises to defer the assignment.
Can you provide the circular code?
s
silly-apple-46154
10/27/2023, 7:05 PM@dry-keyboard-94795 so, the deal is you can't use promises to do it, i went all over the place attempting to figure it out, basically you have to deploy twice to get the configuration of it...
basically here is the deal, i configure many lambdas the lambdas need to have an envVar of the cognito user pool id and user pool client id, there are realistically two options, i create two separate stacks OR i deploy twice and reference the output of the existing deploy.. there are several tickets surrounding doing this behavior in the future but if you deploy cognito with everything else, at the time that it is necessary it won't work (why this is also the case is that cognito is configured to talk to lambda with it's lambdaConfig property), so i have a chicken and egg problem
d
dry-keyboard-94795
10/27/2023, 7:10 PMI took a look at the resource, and was worried you were going to say it's for the lambda config. I recall facing this issue in the past, even with a 2 stage deploy.
dry-keyboard-94795
10/27/2023, 7:11 PMDid you work out setting outputs with
exports
silly-apple-46154
10/27/2023, 7:16 PMi have it working now 😄
d
dry-keyboard-94795
10/27/2023, 7:16 PMthe payload sent to lambda does container the
userPoolIdclientIds
silly-apple-46154
10/27/2023, 7:17 PM Copy code
export default {
cognito: {
userPoolId: cognitoPool?.id,
clientId: cognitoClient?.id,
domainId: cognitoDomain?.id,
},
}; Copy code
const organizationName = pulumi.getOrganization();
const stackName = pulumi.getStack();
const programName = pulumi.getProject();
const currentStack = new pulumi.StackReference(stackName, {
name: `${organizationName}/${programName}/${stackName}`,
});
const cognitoOutputParams : {
clientId: string;
domainId: string;
userPoolId: string;
} | undefined = await currentStack.getOutputValue('cognito');silly-apple-46154
10/27/2023, 7:18 PMbasically, first part creates the lambdas and configures the lambdaConfig for cognito, second deploy will fetch the cognito from the stack reference and assign in the associated env parameters.
silly-apple-46154
10/27/2023, 7:20 PMnow after nearly killing myself all week i have a fully functional deployment stack in pulumi, it has been a nightmare mainly because i couldn't utilize async and so many things i had to abstract out to allow for fetching the string values i provided (pulumi.Output is my arch nemesis)
silly-apple-46154
10/27/2023, 7:20 PMlikewise pulumi.Input 😕
silly-apple-46154
10/27/2023, 7:21 PMthings like this just why...
Copy code
export class Provider extends AWSProvider {
regionName: string;
constructor(name: string, args?: ProviderArgs, opts?: ResourceOptions) {
super(name, args, opts);
this.regionName = args!.region as string;
}d
dry-keyboard-94795
10/27/2023, 7:25 PMcouldn't utilize async?
I've not learned the JS pulumi runtime fully yet
s
silly-apple-46154
10/27/2023, 7:26 PMnope, so basically anything wrapped in a pulumi.Output or pulumi.Input cannot be retrieved until after the end of the execution by the underlying engine so essentially at runtime all .Output and .Input values cannot be accessed
silly-apple-46154
10/27/2023, 7:26 PMeven if the values passed in were strings and are known
silly-apple-46154
10/27/2023, 7:27 PMalmost like a .isKnown property needs to be added so one can actually get the value without any issue
silly-apple-46154
10/27/2023, 7:28 PMlikewise, causes a ton of problems because there are situations where you cannot really use .apply (think domain names whereby records may utilize the same underlying certificate verification procedures... was a nightmare figuring that one out).
d
dry-keyboard-94795
10/27/2023, 7:29 PMyeah, workarounds might be tougher in JS due to code mangling. I've workarounds for lifting Output values in python
s
silly-apple-46154
10/27/2023, 7:47 PMyeah i had attempted a few things to workaround it, unfortunately, it's wrapped damn good and i couldn't get the values out... drove me insane.
d
dry-keyboard-94795
10/27/2023, 7:51 PM Copy code
const foo = pulumi.Output.create("foo");
console.log(await (foo as any).isKnown as Promise<boolean>);
console.log(await (foo as any).promise());dry-keyboard-94795
10/27/2023, 7:51 PMit logs
truefoos
silly-apple-46154
10/27/2023, 7:52 PMhahaha 🙂
silly-apple-46154
10/27/2023, 8:12 PMim going to keep a copy of that thing around