Some of the examples pass options to Python APIs
via `__opts__` instead of `opts`.
The only time `__opts__` is supposed to be used is when
the resource has an existing `opts` parameter,
which is not the case for the resources in these examples.
This updates them to use `opts`.
Resolves#2471
Our documentation for how to use Pulumi with GitHub Actions
included GitHub Workflow files using setup-go@v2
referencing specific Go releases.
[actions/setup-go@v3](https://github.com/actions/setup-go#v3)
added support for a 'stable' (and 'oldstable') alias.
With this alias, the action will always use the latest stable Go release
instead of a specific version.
This updates our GitHub integration documentation
to recommend setup-go v3 and the 'stable' alias
over a specific pinned version.
That leaves this documentation and the sample workflow files
more future-proof as newer versions of Go are released.
* Add blog post entry on automating member account creation in AWS Organizations
Co-authored-by: Christian Nunciato <christian@pulumi.com>
Co-authored-by: Scott Lowe <slowe@pulumi.com>
* Add 'Automating Pulumi Import to Bring Manually Created Resources into IaC'
* Apply suggestions from code review
---------
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Update copy on home page
* Add automation api layout
* Fix typo
* Add some examples
* Address some feedback
* Update homepage with recent changes
* Update slot machine copy
* Address feedback
* Fix headline
* Add templates cta
* Make label smaller
* Update testimonials
* Update themes/default/content/_index.md
Co-authored-by: George Huang <george@pulumi.com>
* Update themes/default/content/_index.md
* Apply suggestions from code review
Thanks Christian
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Apply suggestions from code review
Co-authored-by: Christian Nunciato <c@nunciato.org>
Co-authored-by: aaronkao <aaronkao@users.noreply.github.com>
* Address feedback
* Update themes/default/content/_index.md
Co-authored-by: George Huang <george@pulumi.com>
* Add java example for eks
* Address auto api feedback
* Tighten up some padding and code, use text-lg to align with other sections (#2434)
Co-authored-by: aaronkao <aaronkao@users.noreply.github.com>
Co-authored-by: George Huang <george@pulumi.com>
Co-authored-by: Christian Nunciato <c@nunciato.org>
* initial version
* v2
* adopted codefence suggestion
* inlined pulumi provider boilerplate
* broke apart code example
* added meta image and cleaned up preview.
* addressed review comments
* removed link to github to not compete with the read more link
* Update the date
* Update themes/default/content/blog/pulumi-go-boilerplate-v2/index.md
Co-authored-by: Christian Nunciato <c@nunciato.org>
Some of the documentation for secrets hard-codes
links to the Python APIs.
Replace these with shortcodes for those APIs
that change as different languages are selected.
Additionally, the following changes were made to the shortcodes:
- getsecret, requiresecret, secret-new: teach about Java
- secret-new: Fix Go API -- there's no "NewSecret", only "ToSecret"
Supersedes #2404
One of the snippets for `pulumi login s3://..` does not quote the URI.
This won't work if someone tries to copy and run it because the '&'
will be interpreted as a shell command to start a background process.
Fix by adding quotes around the login command.
Update the Pulumi Fundamentals pathway with a correct environment variable that allows the frontend container to listen on a different port.
Fixes https://github.com/pulumi/devrel-team/issues/485
Signed-off-by: Scott Lowe <slowe@pulumi.com>
Add Go content to the Building with Pulumi pathway. Clean up a few hard link breaks. Fix improper wording. Remove unnecessary duplicate text.
Signed-off-by: Scott Lowe <slowe@pulumi.com>
In the Get Started documentation,
when we tell users to Create a New Project with `pulumi new`,
we include a handful of short paragraphs next to each other
with instructions.
This is not very skimmable:
- keywords like project name/description/stack name
are hidden in the text
- the actual instruction of what to do is also just hidden
in the text
For someone following along, it's better to have keywords
related to prompts they're seeing highlighted,
and to include a sample output they can follow along to.
This changes the create-project sections
of all four Get Started with Pulumi pages
in the following way:
- project name and project description are bold
- change "name of a stack" to "a stack name", and bold "stack name"
- add the output of `pulumi new` after each step;
I've altered the output slightly to not be language-specific
Before this change, only the k8s tutorial included a sample prompt,
but that was at the top of the text rather than interspersed with it.
* add images for final CED update
* add new resources pages for CED workshops
* update CED page with new resources pages, customer stories and recommended sessions sections
* add CED to featured resources
* PR feedback
* add rel=0 to youtube video
