numerous-artist-170508/05/2020, 9:59 AM
, but "do something with x" gets invoked BEFORE the resource creation (I presume as the property is the name and it's available upfront). I tried adding other properties with
resource.Property.Apply(x => do something with x)
, but it seems that, as the name is ready it will be always invoked immediately. Is there a way to wait for the resource to be created to execute some other code? Thanks
sticky-jordan-2715608/05/2020, 5:40 PM
numerous-artist-170508/06/2020, 7:46 AM
does not have an overload accepting
. The workaround could be (not sure if it works) to create a dummy custom resource that depends on the function and use something on its ID output to invoke the get; that would be really awful and I'm not sure it would work as probably also that ID would be known upfront.
tall-librarian-4937408/06/2020, 8:13 AM
approach doesn’t work. Are you tupling a property that is unknown before deployment?
numerous-artist-170508/06/2020, 8:41 AM
as that is surely provided by Azure and it worked. It's still a bit hacky and I'm not sure it will work in all cases, but it's good enough for now.