Revamp AWS quickstart to focus on creating custom API #507
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Pete Lumbis <[email protected]>
plumbis
changed the title
Signed-off-by: Pete Lumbis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the AWS Quickstart guide in master and v1.13 to use the Upbound family providers and changes the focus from being about Crossplane components to focusing on building and using a custom API with Crossplane.
The main motivation for the change is the new /concepts topics pushed in #475 gives us much better places to point people to discuss the details of the Crossplane components. We can have the quickstart focus on outcomes instead.
This also deletes part 3 of the quickstart that covered patching and packages. Patching is now covered in part 2 and packaging isn't required for a "quickstart".
Signed-off-by: Pete Lumbis [email protected]