DOC-3411-WinRM Secret #2493
DOC-3411-WinRM Secret #2493
Conversation
roshnisarangadharan
added
documentation
DO NOT MERGE
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
1 similar comment
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
| sidebar_position: 4 | ||
| --- | ||
|
|
||
| Use these steps to add a WinRM key that can be referenced in Harness entities. |
There was a problem hiding this comment.
WinRM credential key
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
1 similar comment
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/shell-script-step.md
Outdated
Show resolved
Hide resolved
| 4. Enter a **Host Name** of the remote server you want to connect to. For example, if it is an AWS EC2 instance, it might be something like `ec2-54-175-135-106.compute-1.amazonaws.com`. | ||
| 5. Select **Test Connection**. | ||
|
|
||
| If the test is unsuccessful, you might see an error stating that no Harness Delegate could reach the host, or that a credential is invalid. Make sure that your settings are correct and that a Harness Delegate is able to connect to the server. |
There was a problem hiding this comment.
What does "you might" convey? Even if those two reasons are the only reasons for the test's failure, does it mean that there's only a possibility that the UI will display those associated messages? Or does it mean that, if the actual reason is one of the two listed reasons, then a message is definitely shown, but there could be other reasons and other (or no) associated messages?
The issue might be with beginning with "If the test is unsuccessful". The reader begins to expect a comprehensive list of reasons. Can we rewrite to "If a message stating that no Harness Delegate could reach the host, or that a credential is invalid, is displayed, verify delegate-to-host connectivity or the credential settings, respectively. (Just a suggestion. Feel free to rewrite in your own way.)
In any case, if the UI displays appropriate messages, and I think it does in this case, we shouldn't have to describe such issues in the documentation at all.
There was a problem hiding this comment.
Implemented your suggestion
Co-authored-by: Deepak Bolangady <deepak.bolangady@harness.io>
docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/shell-script-step.md
Outdated
Show resolved
Hide resolved
docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/shell-script-step.md
Outdated
Show resolved
Hide resolved
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
1 similar comment
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
Add a topic to cover WinRM secrets.
In the PR, #2389, a placeholder was added to add links to WinRM secrets but we don’t have a topic to redirect to. Add the WinRM secrets topic link to this topic.