https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# python
s
This message was deleted.
e
Implement read: 
def read(self, id_: str, props: Any) -> ReadResult:
Get just resolves to a ReadResource operation, which just gets the engine to call "read" on the provider. You'd have to write the get functions by hand because it's not part of the dynamic provider sdk but should be doable from copying how RegisterResource in dynamic.Resource works and how a normal resource get function looks.
Having said all that. It's probably a lot easier to just have a normal dynamic resource that you "Create" but actually just gets the info and doesn't delete the resource. 
get
with dynamic isn't really tested and we don't have any examples of it.
c
Thank you very much! I like the idea of Dynamic Resource that retrieves data.
@echoing-dinner-19531, one more question, how can I ensure that I will get the up-to-date information each time I execute 
pulumi up
? I assume that my dynamic resource will not get updated once I created it.
e
It's a little bit of a hack, but you could implement Diff so that it always returns that there's a change that needs Update so that every 
up
the engine calls the Update method.
This is good use cases for us re-thinking dynamic providers and supporting something like this more natively.
c
And what do you think about putting a 
timestamp
into the resource ID? IMO this will do the trick 😉
e
I think that might trip up some replace logic, I'd lean towards just returning a change from Diff
7 Views
Open in Slack
PreviousNext
Powered by