Ian Wahbe
Ian Wahbe
Hi @lv12312 Thanks for letting us know about this. I was about to suggest that you file an upstream issue, but I see that you [already did so](https://github.com/aliyun/terraform-provider-alicloud/issues/7348). If upstream...
> @iwahbe So this is essentially "support monorepos for Registry docs", or is there more to is than that? No, that's about it.
I don't think we need this preview anymore.
I strongly agree with @cnunciato's opposition to a doc-ops and doc-ops-critical channel. I'd much rather focus on making sure we only get notifications that we actually care about.
I havn't dug into search at all. It sounds like we need a general keywork/tag mechanism, and that [what we have](https://github.com/pulumi/pulumi-scm/blob/0254ffa3e5e71f01cd9f7ba7686061fd9dbab129/provider/resources.go#L66-L71) isn't doing it.
We should be able to run a live test of this now. The live registry should have all the providers.
We need the special tags handling because terraform-provider-aws's native tags handling relies on refresh for correctness, and so doesn't work for most Pulumi users.
> > We need the special tags handling because terraform-provider-aws's native tags handling relies on refresh for correctness, and so doesn't work for most Pulumi users. > > @iwahbe can...
I didn't know that this was possible. It's definitely worth adding the the `## Integration with 3rd Parties` section of the README.md!
Can you give us an example so we can repro locally? What is the blocking workflow? Is it just `pulumi up` on an unchaged program? There are a lot of...