Per: https://www.pulumi.com/docs/intro/languages/go/
> Pulumi supports writing your infrastructure as code using the Go language. Go 1.16 or later is required.
The basic `pulumi new go` setup fails to preview when using Go < 1.16.x in the provided GitHub Actions templates.
* Update SSO configuration instructions for Okta
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
Co-authored-by: Christian Nunciato <christian@pulumi.com>
Even after breaking the Programming Model content down, this Resources page still contained a *lot* of core content. This made a lot of important features feel very "hidden", like resource options, components, dynamic providers, and more.
It also led to suboptimal search results, both in Google and in our own internal site search, because searches for specific concepts (like "pulumi aliases") would return the "Resources" page, which didn't even rank particularly well as it doesn't "feel" like definitive content for this specific topic.
This change breaks this page into 18 separate pages. It keeps the "Custom Resource" content in the main Resources page (since that content is nearly entirely actually not specific to Custom Resources anyway), pulls the Custom Resource, Resource Providers and Dynamic Providers content into separate top level items, and pulls the Resource Options content into it's own index with a separate page per resource option.
Some of the resulting pages are fairly light in content, but this actually offers room to flesh these out more fully now that they have room to breathe.
Reading through this content as part of the refactor, there is quite a bit of cleanup we could still do here. I took a few liberties to clean up some things as part of this, but mostly focused on the refactor instead of changes to prose.
This also introduces a set of client-side redirects to the resources page, so that each of the previous anchors which now lives elsewhere will get redirected in the client, following the same strategy used in the Programming Model page refactor.
* Add section describing how to invite new members to an organization.
* Linting fixes to organization invitation content.
* Update themes/default/content/docs/intro/console/organizations.md
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* Incorporate feedback to improve member invite section; add details about link for SSO.
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* Add languages for first example
Remove in-depth TS specific lambda creation examples and prefer
referencing the existing lambda documentation.
* Update API Gateway routes guide
* Re-order and rename sections
- Make titles shorted to ease navigation
* Update lambda request authorizer section
* Remove token authorizer example
- Just leave the request authorizer with a note about other types.
- Remove information about helper functions.
* More polishing of first sections
* Complete request validation examples
* Rework API Keys guide
* Update OpenAPI single route examples
* Update whole-api swagger examples
* Finish up API Keys example
* Update DNS setup
- Use an example domain that doesn't exist.
* Work around number lint failure
* Adopt suggestions from @susanev
- Use note styling instead of quotes.
- Tweak links.
* Pull changes from testing examples
61f128aa0b
* Use fnOutput forms to simplify kubernetes/apps.md
* Update crosswalk/aws/eks.md
* Upd azure/review-project.md: skip go as it flags off fnOutput
* Update crosswalk/aws/vpc.md
* Update aws/how-to-guides/ec2-webserver.md
* Update guides/adopting/from_aws.md
* PR feedback on TypeScript
* Revert unfortunate change
