Skip to content

Conversation

@stefnestor
Copy link
Contributor

Refactors filebased realm page for clarity & expands examples to include file-based role.yml definitions needed to recovering security.

Relates #2479

@stefnestor stefnestor requested a review from a team as a code owner August 9, 2025 18:08
@stefnestor stefnestor added the enhancement New feature or request label Aug 9, 2025
@stefnestor
Copy link
Contributor Author

👋 @elastic/admin-docs , I did try to figure out the links myself from Brandon's earlier guidance but apparently could use more help, sorry 🙂🙏

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

I think that the information about recovering security does not necessarily belong in this doc. while the file might need to be refactored, introducing this information and the role information blows up the scope of the page. the recovery use case might work better as a standalone tutorial.

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

see comment

@stefnestor stefnestor requested a review from a team as a code owner September 13, 2025 16:00
@stefnestor
Copy link
Contributor Author

Thanks, @shainaraskas ! And apologies for delay on my side. I have ported into a troubleshooting guide (with some minor edits left on first page). 🙏

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

generally looks really good. I've edited the recovery tutorial a little for grammar and flow

questions:

  • is the person always going to need the allow_restricted_indices permission? should we guide them when they should/should not use it?
  • can we give them next steps, e.g. testing of this user, recovery tasks ...?

let me know how badly I butchered things with my edits

@github-actions
Copy link

github-actions bot commented Sep 16, 2025

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

link fix suggestions

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

if dev is happy we're good to merge

Copy link
Contributor

@tvernum tvernum left a comment

Choose a reason for hiding this comment

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

Overall this looks good and is a very welcome addition. I had a few minor suggestions to make the wording more accurately reflect the how the underlying features work.

@stefnestor stefnestor merged commit 963f5ae into elastic:main Sep 26, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants