Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Add clarity around AWS classic vs native #2939

Merged
merged 2 commits into from
Jun 6, 2023
Merged

Conversation

mnlumi
Copy link
Contributor

@mnlumi mnlumi commented May 26, 2023

Description

Checklist:

  • I have reviewed the style guide.
  • If blogging, I have reviewed the blogging guide.
  • I have manually confirmed that all new links work.
  • I added aliases (i.e., redirects) for all filename changes.
  • If making css changes, I rebuilt the bundle.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit 9eb81a3 is ready! 🎉

http://pulumi-hugo-origin-pr-2939-9eb81a3a.s3-website.us-west-2.amazonaws.com.

Copy link
Contributor

@susanev susanev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally don't think the last sentence is needed in this context or at least the part before try, but don't feel strongly. @anita-trimbur what do you think?

@pulumi-bot
Copy link
Collaborator

Your site preview for commit 0c270fd is ready! 🎉

http://pulumi-hugo-origin-pr-2939-0c270fdb.s3-website.us-west-2.amazonaws.com.

@mnlumi mnlumi merged commit f5aec6d into master Jun 6, 2023
@mnlumi mnlumi deleted the mnlumi/aws-provider-clarity branch June 6, 2023 16:27
@github-actions
Copy link

github-actions bot commented Jun 6, 2023

Site previews for this pull request have been removed. ✨

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants