hey, I noticed that neo’s review that happens auto...
# pulumi-neo
h
hey, I noticed that neo’s review that happens automatically when you have previews enabled on github deployment settings often (always? not sure) doesn’t see resources being created. is this a known bug? i often see it saying that preview doesn’t show some kind of resource being created when in reality it does. you can see one such occurrence in the attached screenshot. it’s not a big deal to me but I’m curious if this perhaps is how it works for everyone or maybe it’s something specific to my setup
m
Hi @hundreds-processor-20948 So, preview said no changes but applying it created that gcp resource? Did anything change between in the PR or in the cloud and how long between preview and up?
h
So, preview said no changes but applying it created that gcp resource?
no no no. preview DID show this change. and you can see that in the screenshot. it shows both preview and neo’s review (saying it’s not in that preview seen above) that gets posted via pulumi’s github app on a PR.
but actually I do have a theory now. since there’s no way to do run
pulumi preview
or
pulumi up
with
--refresh
in pulumi deployments (or at least i haven’t found one) i run
pulumi refresh
as pre-run command. this refresh shows up as another update in a deployment. perhaps neo confuses the output of that update with the output of the actual preview?
m
I can flag it to someone on neo team @hundreds-processor-20948
🙌 1
Fix is being worked on
🙌 1