Marcos Candeia

@dsherret I couldn't make it work either, it's not clear to me if I should run `deno cache --vendor main.tsx` and then I can run with `--no-remote` ? previously It...

I tried with `--vendor` using `deno run --vendor main.tsx` and it seemed to work, but with a large project I have to remove node_modules/.deno to work, probably something that changes...

ping @dsherret

Thanks, will check @dsherret

Now it's a different problem, Tested with: https://github.com/deco-sites/start (using Deno 1.39.1) `deno cache --vendor dev.ts` will generate a vendor folder with no import_map generated. I don't know if I did...

> Yeah, that's expected. The --vendor feature (recommended use as { "vendor": true } in deno.json) is a completely different more reliable way of doing vendoring that does a cache...

Just to let you know. I changed my approach because I couldn't make it work with vendor command nor --vendor option. It was much simpler to just zip the entire...

> Hi @mcandeia, there was an issue with Istio degradation due to annotations removal in #172 so I reverted the #166. My apologies for this. I'm re-opening your issue but...

In addition, the latest operator version is not working with dapr and I had to pin the 0.0.8 release.

I'd prefer the option 1, just a qq: Assuming that the key pair will be rotated with some frequency (so the app should fetch jwks.json not only on the startup...