Hi folks :wave::skin-tone-2: I'm in the last steps...
# package-authoring
b
Hi folks 👋🏻 I'm in the last steps for the initial release of the
pulumi-fortios
provider and I want to add (copy) a couple of
how-to
documents from the upstream TF provider. I would like to create a section where these documents are collected, just like the Azure Native Provider (ref. screenshot). I have seen that the documents for the Azure Native Provider are stored directly in the
pulumi/docs
repository (ref. screenshot). However, the Fortios provider is hosted on #pulumiverse. So how can I create this section without having to add the documents to the pulumi/docs repository?
l
@big-architect-71258 this needs to be fixed for that: https://github.com/pulumi/registry/issues/3159
b
@limited-rainbow-51650 added a comment, because IMHO the
registrygen
tool must be changed. Not the registry itself. @billowy-army-68599 can prove me wrong 🤗
Because we must enumerate the files in the
docs
folder, we could use the TREE API of GitHub https://docs.github.com/en/rest/git/trees?apiVersion=2022-11-28 in
registrygen
Couldn't resist 😂 https://github.com/pulumi/registrygen/pull/19 @billowy-army-68599 @ancient-policeman-24615 anyone up for a review?