Resolve name collision between S3 and Lightsail in quickstart #811
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.
Description of your changes
Fix #590: S3 and Lightsail APIs have their own “buckets” resources. Quickstart document creates an S3 bucket. When
kubectl get buckets
command is run, though, Lightsail resources are listed. Such behavior confuses users, especially newcomers to crossplane, who expect to see their S3 buckets instead.I have:
make reviewable test
to ensure this PR is ready for review.I couldn't run
make reviewable test
, because of IS#737. I hope that updating only documentation won't cause any problems.How has this code been tested
I've followed quickstart document and manually run shell commands. I've used a local kind cluster.