i'm trying to follow this: <https://www.pulumi.com...
# generalb
better-rainbow-14549
07/26/2019, 3:02 PMi'm trying to follow this: https://www.pulumi.com/docs/reference/programming-model/#dynamic-provider-examples
but i can't see how i would expose further properties? I want to generate two related numbers at create time, and then be able to access them in future. how is that done please?
the other examples here aren't really helping: https://github.com/pulumi/pulumi/blob/master/examples/dynamic-provider/simple/index.ts
t
tall-librarian-49374
07/26/2019, 3:18 PMHave a look at this example: https://github.com/pulumi/examples/blob/master/azure-ts-dynamicresource/cdnCustomDomain.ts
b
better-rainbow-14549
07/26/2019, 3:19 PMoh that's far more complete thanks
better-rainbow-14549
07/26/2019, 3:31 PMstill struggling to see how to populate the properties for future runs
better-rainbow-14549
07/26/2019, 3:31 PMhow / when is e.g. the property on line 269 populated with the value from the state
t
tall-librarian-49374
07/26/2019, 3:47 PMIt's assigned to outs in
createb
better-rainbow-14549
07/26/2019, 3:47 PMi mean on future runs though
t
tall-librarian-49374
07/26/2019, 3:47 PMThey will be saved in state
b
better-rainbow-14549
07/26/2019, 3:47 PMe.g. if i add another resource later that depends on that property
better-rainbow-14549
07/26/2019, 3:48 PMyes but when is it populated back from state
t
tall-librarian-49374
07/26/2019, 3:48 PMthat should be taken care by pulumi
b
better-rainbow-14549
07/26/2019, 3:53 PMcan i spam a super simple example i'm not getting anywhere i think i must be missing something fundamental
t
tall-librarian-49374
07/26/2019, 3:54 PMsure, put it on github or gist
b
better-rainbow-14549
07/26/2019, 3:54 PMbetter-rainbow-14549
07/26/2019, 3:55 PMso in my state file I can see the token was created properly and all the outputs are popualted
t
tall-librarian-49374
07/26/2019, 3:58 PMah, I suspect you need to do one more thing: initialize those props in constructor, see https://github.com/pulumi/examples/blob/master/azure-ts-static-website/staticWebsite.ts#L72
b
better-rainbow-14549
07/26/2019, 4:00 PMahhhh thanks a lot
better-rainbow-14549
07/26/2019, 4:00 PMyep working now 👌
t
tall-librarian-49374
07/26/2019, 4:03 PMI'm actually not sure why this is required. Might be worth filing an issue
w
white-balloon-205
07/26/2019, 4:09 PM
I am actually just about to do some updates to these docs today - and will see about making this point clearer.
b
better-rainbow-14549
07/30/2019, 4:52 PMI've upgraded pulumi today - from .16 to .21 and then to .26 and then to .27
better-rainbow-14549
07/30/2019, 4:52 PMand on the .16 to .21 my partnerToken from that gist was reset and regenerated, and it was reset to undefined.undefined from .26 to .27
better-rainbow-14549
07/30/2019, 4:53 PMis this a bug in pulumi or is there a flaw in my dynamic resource?
better-rainbow-14549
07/30/2019, 4:53 PMhttps://gist.github.com/oliverholliday/45bab094c85cc726d1754f0b3b3691bf that was the gist
w
white-balloon-205
07/30/2019, 5:01 PM
I'm not sure I follow exactly what you saw happen. Was this resource replaced or updated in any of the deployments? If so, what diffs were shown?
white-balloon-205
07/30/2019, 5:01 PM
Could you open an issue with any details?
b
better-rainbow-14549
07/30/2019, 5:02 PMwhat i saw in the diffs was that the serialized "_provider" changed
better-rainbow-14549
07/30/2019, 5:02 PMand essentially its acted as if i recreated the resource but i didnt
better-rainbow-14549
07/30/2019, 5:02 PMwell, from .16 to .21 it did
better-rainbow-14549
07/30/2019, 5:02 PMbut from .26 to .27 it's not recreated it and it's just blanked out the outputs
better-rainbow-14549
07/30/2019, 5:16 PMbetter-rainbow-14549
07/30/2019, 5:56 PMsorry the .16 to .21 was a mistake on my part - it seems we destroyed the entire stack, but the .26 to .27 is still an issue