@clever-plumber-29709 Thanks for reporting these issues and sorry you ran into problems here. I opened https://github.com/pulumi/docs/issues/5199 to track these issues. Note: I see the arg

name/resource_name

shown with the required asterisk when cycling through the various languages on the ECS service page. Is there a specific place on the page where you didn’t see this?

Hi @limited-planet-95090, I just came across some not-quite-idiomatic code in the get-started docs. Wondering if an issue or a PR is preferred?

Hi folks! 👋 We just merged a change that moves much of our documentation out of pulumi/docs and into a new repository at https://github.com/pulumi/pulumi-hugo. As of now, pulumi/docs contains only our generated documentation, like CLI docs, SDK docs, and the tutorials we generate from https://github.com/pulumi/examples. Everything else, including the blog, landing pages and other reference documentation, is now managed in pulumi/pulumi-hugo. The contribution workflow is still mostly the same, but it does mean that any open PRs will need to be moved to the new repository. If you have any questions or run into any issues, please let us know. Thanks as always for your contributions and support!

Noticed a small typo on the website: https://www.pulumi.com/docs/guides/pulumi-packages/#get-started While the link is correct, the link text for

Go

is wrong:

pulumi/pulumi-component-provider-ts-boilerplate

are the pulumi docs derived from the terraform docs? 🤔 I noticed

<mailto:jdoe@hashicorp.com|jdoe@hashicorp.com>

on https://www.pulumi.com/docs/reference/pkg/azuread/user/#example-usage which matches up with https://registry.terraform.io/providers/hashicorp/azuread/latest/docs/resources/user 😉

Hey! I have a feature request: it would be super cool if all code snippets switched to a given language when selected in one place ,and even cooler if they stayed that way across page reloads and navigation to other pages. Thoughts?

Hi I’m looking at this document about CICD assistant, but cannot find the same page on Pulumi console, the closest I can get is the “Configure Integration” but it also looks quite different from the figures in the document. It seems it only redirect to other documents instead of starting a wizard guide. Thanks in advance!

@gifted-cpu-92480 the CI/CD integration assistant is only available in organizations, not personal accounts. You can create an org using the drop-down next to the pulumi logo at the top of the page.

Got it, thanks for the quick reply!

Over the past several days I’ve noticed that it takes up to several minutes to load a single documentation page, and I get this warning at least twice for each page I visit. At first I thought it’s a problem with my connection, but this continues to happen while other pages I visit are snappy and download quickly. Has anybody else experienced this?

Yes I'm seeing the same thing on macOS 11.3.1, Chrome v90.0.4430.212 - the s3 Bucket docs page loads atrociously slow, if at all, on Chrome, taking 30-60 seconds to finish loading. I'm on a rather beefy workstation. The docs seems to work dramatically better in Safari.

would you be able to post the page performance from chrome?

Thanks for reporting this. We’ve had a couple of internal reports as well and are currently investigating: https://github.com/pulumi/docs/issues/5959

Thanks everyone! Let me know if you need any data, and I’ll try to supply that.

Hi #docs hopefully this is the right place to report this. There seems to be a small discrepancy in the Azure B2CTenant resource C# reference page (https://www.pulumi.com/docs/reference/pkg/azure-native/azureactivedirectory/b2ctenant/#create-tenant). Name and Tier inputs should be:

Name =  AzureNative.AzureActiveDirectory.B2CResourceSKUName.Standard,
                Tier = AzureNative.AzureActiveDirectory.B2CResourceSKUTier.A0,

instead of raw string I believe.

Nevermind, I found the "Request a change" link and created this issue: https://github.com/pulumi/pulumi-hugo/issues/277

Awesome. Thanks @flaky-school-82490!

Notice a small typo, the word "access" is duplicated.

Just want to say I enjoy the new font choice in the reference documentation.

the documentation generation for the aws.wafv2 resource appears to have a bug that keeps causing the page to freeze/crash

Is there a plan/road-map to add support for Create a service account as part of current @pulumi/datadog? Use case is that we would like to have in future AM as code for both users and service accounts with Pulumi for Datadog, actions like creating service-accounts, users, API keys…etc.

FYI, eks package link on https://www.pulumi.com/docs/reference/pkg/ is broken after the new registry release. It now goes to: https://www.pulumi.com/registry/packages/eks/api-docs//api-docs

I find it really difficult to get to the reference documentation from the homepage. I have provided feedback to any of the surveys about improving the documentation, and I believe it's gotten worse to navigate (but the search is definitely better). 1. https://www.pulumi.com/ -> 2. https://www.pulumi.com/docs/ -> a. Click AWS get to https://www.pulumi.com/docs/get-started/aws/ -> which dumps me in a tutorial I don't need. As a user coming back to reference documentation, almost everything in the sidebar above the fold is useless to me b. forget this dead-end, look for "Reference" 3. Scroll all the way to the bottom of the side bar (which is basically the middle of the webpage), click "API Reference" -> https://www.pulumi.com/docs/reference/pkg/ 4. Click AWS get to https://www.pulumi.com/registry/packages/aws/ -> click a tab in the middle of the page "API docs" 5. Arrive at what I was hoping for https://www.pulumi.com/registry/packages/aws/api-docs/ Finding the Pulumi SDK seems even more difficult than AWS. It's in the bottom of the page here without any logos to catch your attention https://www.pulumi.com/docs/reference/pkg/#package-documentation The easiest way to enter the Pulumi reference documentation seems to be through https://www.pulumi.com/docs/reference/ -- but then the presentation of these docs is different than the other reference documentations. There is a jump-page to the SDK of choice, rather than the unified language views of the other reference documentation.

Is there something wrong with my browser, or this page? https://www.pulumi.com/registry/packages/aws/api-docs/provider/

It’s been a few months, but I’d like to reiterate @millions-furniture-75402’s pain. I have been a Pulumi user for several years now, and in the beginning, I found the Pulumi docs to be amazingly simple and helpful. There was a very simple set of “concepts” and all of the API docs were excellent reference materials. For 99%+ of my Pulumi docs visits, the only page I really want to get to is this page: https://www.pulumi.com/docs/reference/pkg/ , but it’s always so hard to find. I appreciate that those APIs have been put all onto one page, but the link to it is buried “beneath the fold” and has to be scouted out in the bottom left corner of the Docs page. I don’t know the right terminology for this, but it seems to me that there’s a big difference between what I think of as “Docs” and what I think of as “Guides”. Currently, the Pulumi “Docs” section heavily favors “Guides,” but those become much less useful after you already know how to use Pulumi. It feels a bit like going through an onboarding flow every time I’m trying to find the API reference docs. Of course, I don’t have the context that you surely do about usage, but from my perspective, it would be very helpful to have the link to the “Reference” and/or “API Reference” sections be treated differently than all of the guides. A couple of suggestions might be: • Make “Docs” dropdown in the header that has “Guides” and “Reference” called out separately • Or maybe add a “Reference” button next to the “Get Started” button on the Documentation homepage for people who aren’t looking for the full flow. • Maybe the “References” submenu on the left bar gets moved up above the fold. Last thing — I think that there’s an additional UI problem that makes it hard to find the docs. I’ll walk you through the flow here so you can replicate the problem in your browser because it’s kind of hard to explain: 1. https://www.pulumi.com/ -> 2. https://www.pulumi.com/docs/ -> 3. Put your mouse in the middle of the page and scroll down to the footer a. Now, look at the left sub-menu column. It’s cut-off (unless you have a huge browser window). The “References” section is beneath that cut-off. b. The only way to get to “References” is to put your mouse over the left sub-menu and scroll down within that menu. That is not obvious unless you know that’s a scrollable container. I think that last point is likely why I end up so lost so frequently. I click “Docs” and I look around for what I’m trying to find, but I don’t see it. It wasn’t actually until today (as I was writing this) that I realized that the left bar could scroll. If I’ve done it before, it’s not even an action that I registered. I love the product, and I hope that’s helpful. It’s all meant in the spirit of feedback and not complaining.

Hi, I'd like to edit something in the docs, but the "edit this page button" leads to a 404 on Github. My little edit is for the "Host a Static Website on Amazon S3," which says that "The Resources tab in the Pulumi Service has a link to the AWS console for the provisioned EC2 instance.", but there are no EC2 instances in the tutorial. 🪣☺️ https://www.pulumi.com/registry/packages/aws/how-to-guides/s3-website/

Hi, I just started to look on the Pulumi. It looks very nice but I’m a bit lost on how to structure properly the code. There are any best practices for it? I’m working on AWS and Go. Shall I create new module for new type of services in AWS? Shall I do it a bit like in Terraform? Thanks!

Hi folks, there seems to be a problem with the manual for the Command provider: The web page seems to be truncated after the "Inputs" section on https://www.pulumi.com/registry/packages/command/api-docs/local/command/#inputs . What is the best place to flag this?