Adding troubleshooting steps for DNS issues to readme #128
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
tyler-romero
reviewed
Nov 8, 2024
| @@ -69,6 +69,65 @@ deployment. If you want to make modifications to the edge endpoint code and push | |||
| image to ECR see [Pushing/Pulling Images from ECR](#pushingpulling-images-from-elastic-container-registry-ecr). | |||
|
|
|||
|
|
|||
| ## Troubleshooting Deployments | |||
There was a problem hiding this comment.
nit: Very general headline for a very specific issue - what if we added another more specific H3 heading under Troubleshooting deployments and then nest everything below under that? Leaves room for other troubleshooting tips as well.
tyler-romero
approved these changes
Nov 8, 2024
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.
Adding some troubleshooting steps based on what I learned during Omnicell's deployment.