Skip to content

Conversation

@mailahmeduk
Copy link
Contributor

Customer needs document update for handling special characters and how we can use the echo command to enter the password.

  • Have you signed the contributor license agreement?
  • Have you followed the contributor guidelines?
  • If submitting code, have you built your formula locally prior to submission with gradle check?
  • If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
  • If submitting code, have you checked that your submission is for an OS and architecture that we support?
  • If you are submitting this code for a class then read our policy for that.

Customer needs document update for handling special characters and how we can use the echo command to enter the password.
@elasticsearchmachine
Copy link
Collaborator

@mailahmeduk please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.1.0 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Apr 22, 2025
@mailahmeduk mailahmeduk added the >docs General docs changes label Apr 22, 2025
@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team and removed needs:triage Requires assignment of a team area label labels Apr 22, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@geekpete
Copy link
Contributor

geekpete commented Apr 22, 2025

The only change I would suggest is to put this in an admonition paragraph (prefix with NOTE: or appropriate admonition type), so that this advice stands out in the page.:
https://github.com/elastic/docs?tab=readme-ov-file#admonition-paragraphs

Or alternatively this section might go into an admonition block:
https://github.com/elastic/docs?tab=readme-ov-file#admon-blocks

and pick an appropriate level of admonition to use.
Some advice on admonition levels I saw was:

In software, we more typically think of the potential hazard to your data:
WARNING you could permanently lose data or leak sensitive information.
IMPORTANT ignoring the information could impact performance or the stability of your system, but your data is not at risk.
NOTE a relevant piece of information, but there are no serious repercussions if you ignore.
TIP a piece of advice intended to help you make better choices in how you use the feature.

so probably either NOTE or IMPORTANT based on the impact that might occur if the characters are not correctly escaped.

@leemthompo
Copy link
Contributor

I think in this we should move the guidance out of the Examples section and put it in a standalone section titled "Handling special characters", just after Parameters:

  • that way we don't need to use admonitions just to make it stand out
  • users will know about working with special characters before jumping into examples

@leemthompo leemthompo added auto-backport Automatically create backport pull requests when merged v9.0.0 labels Apr 22, 2025
@leemthompo leemthompo self-assigned this Apr 22, 2025
@leemthompo
Copy link
Contributor

thanks @mailahmeduk! all need to do now is move the new section up before the Examples section

Moving the section out of Examples as advised.
Copy link
Contributor Author

@mailahmeduk mailahmeduk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. @leemthompo
Made changes as advised.

@mailahmeduk
Copy link
Contributor Author

Can you please review the syntax, something doesn't look right.
image

@leemthompo
Copy link
Contributor

@mailahmeduk the docs markdown syntax won't render nicely in the Github preview, but you can see it works as expected in the docs preview :)
Screenshot 2025-04-22 at 11 05 30

@leemthompo leemthompo removed the request for review from colleenmcginnis April 22, 2025 14:26
Copy link
Contributor

@leemthompo leemthompo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, provided @geekpete is happy :)

Copy link
Contributor

@geekpete geekpete left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@leemthompo leemthompo enabled auto-merge (squash) April 23, 2025 07:34
@leemthompo leemthompo merged commit 98a3719 into main Apr 23, 2025
7 checks passed
@leemthompo leemthompo deleted the mailahmeduk-patch-1 branch April 23, 2025 07:40
@leemthompo
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
9.0

Questions ?

Please refer to the Backport tool documentation

leemthompo added a commit to leemthompo/elasticsearch that referenced this pull request Apr 23, 2025
…echo command to enter the password. (elastic#127135)

* Update elasticsearch-keystore.md

Customer needs document update for handling special characters and how we can use the echo command to enter the password.

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update elasticsearch-keystore.md

Moving the section out of Examples as advised.

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

---------

Co-authored-by: Liam Thompson <[email protected]>
(cherry picked from commit 98a3719)
elasticsearchmachine pushed a commit that referenced this pull request Apr 23, 2025
…echo command to enter the password. (#127135) (#127217)

* Update elasticsearch-keystore.md

Customer needs document update for handling special characters and how we can use the echo command to enter the password.

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update elasticsearch-keystore.md

Moving the section out of Examples as advised.

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

* Update docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md

Co-authored-by: Liam Thompson <[email protected]>

---------

Co-authored-by: Liam Thompson <[email protected]>
(cherry picked from commit 98a3719)

Co-authored-by: Ahmed Khan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >docs General docs changes external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Docs Meta label for docs team v9.0.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants