* Update getting started guides for dotnet 6 using newer templates
* lint
* update ec2-webserver how-to guide for csharp
* Fix inconsistencies found by Mikhail 🙏
* Retarget YAML button on SDK home page
.. in sympathy with this menu change:
https://github.com/pulumi/docs/pull/7764
* Remove the implicit Pulumi YAML spec menu item
The PR https://github.com/pulumi/docs/pull/7764 adds a menu item
pointing at the Pulumi YAML spec, from the SDK part of the navigation
menu; this commit removes the `menu` stanza from the doc file itself,
which would normally generate a(nother) menu item for itself.
Mysteriously, the implicit menu item appears in previews but not in the
live site. Removing it will at least make sure it doesn't accidentally
appear at some later time.
Signed-off-by: Michael Bridgen <mbridgen@pulumi.com>
This adds the Pulumi YAML spec, as taken from
https://github.com/pulumi/pulumi-yaml/blob/main/README.md
to the reference docs part of the website, and links to it from the
intro part, navigation, and reference home page.
Signed-off-by: Michael Bridgen <mbridgen@pulumi.com>
* Add EKS Anywhere blog post
* Add a meta image
* Apply suggestions from code review
Co-authored-by: isaac-pulumi <59850911+isaac-pulumi@users.noreply.github.com>
Co-authored-by: isaac-pulumi <59850911+isaac-pulumi@users.noreply.github.com>
* rough draft skeleton for community page
* updates copy + adds buttons
* adds newline to appease linter
* closing tags will be the death of me
* once again appeasing the linter
* changes youtube link directly to contribex playlist
* Wrestle the buttons
* adds community page to main nav
* formatting
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Add a blog post showing how to use Pulumi and Ansible together
* Fix lint errors
Apparently pulumi convert likes to leave behind trailing
spaces for C# files! :-)
* Use consistent IP addresses
* Update links now that examples are live
* Apply suggestions from code review
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Incorporate some suggestions
* Describe cattle vs pets
* Fix bare URLs
* Remove trailing slashes
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Add PULUMI_TEST_MODE to guides/testing/unit
I was pulling my hair out trying to figure out why `pulumi.isDryRun`
was returning `false` when I was running my unit tests, given that
[the docs on the method][1] say:
> Note that we always consider executions in test mode to be
> “dry-runs”, since we will never actually carry out an update, and
> therefore certain output properties will never be resolved.
I’m still not sure if/where there is any canonical documentation on
“test mode” but I feel that it should probably always be enabled when
running unit tests. I’d prefer that there be a programmatic/imperative
way to enable it, e.g. `runtime.setDryRun(true)` or something similar,
but in lieu of that I feel the examples should include setting the env
var so as to plant seeds of awareness about this feature and how it
works.
[1]: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/#isDryRun
* Revert "Add PULUMI_TEST_MODE to guides/testing/unit"
f4adeec976811d64fe066b5084a9eeaf91b63814
As per discussion in pulumi/pulumi-hugo#1642
* guides/testing/unit: show how to set dryRun flag
Which, as per the discussion in pulumi/pulumi-hugo#1642, should
really/probably be renamed to `isPreview` or something along those
lines.
Anyway, it looks like the C# example already includes passing a value
for this flag, and I don’t know enough Go to add it to the Go example.
Now that I’m writing this commit message, the situation with `dryRun`
is confusing enough (especially given the docs on `runtime.isDryRun`)
that it could probably merit adding a small dedicated section to this
page. I’ll ask in the PR whether that’d be desirable.
* guides/testing/unit.md: better description of a flag
Co-authored-by: Ian Wahbe <ian@wahbe.com>
Co-authored-by: Ian Wahbe <ian@wahbe.com>
