Update efs-csi.adoc #846
Open
Update efs-csi.adoc #846
+7
−7
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
There was a typo on the documentation where Step 3 provided a Note stating that Fargate does not require the creation of the EFS CSI Driver where it should listed under Step 2
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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.
There was a typo on the documentation where Step 3 provided a Note stating that Fargate does not require the creation of the EFS CSI Driver where it should listed under Step 2
Issue #, if available:
Step 3 provides guidance on creating an EFS Volume and provides note stating that this step is not necessary for Fargate and Fargate does not require installation of EFS CSI Driver -- this should be outlined in Step 2 instead.
Description of changes:
Proposed movement of Note to Step 2 instead of Step 3 as it is misleading.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.