Pinging @elastic/es-security (Team:Security)

Hi @sqren, I've created a changelog YAML for you. Note that since this PR is labelled >deprecation, you need to update the changelog YAML to fill out the extended information sections.

I think we should use the next major release instead of 9.0 since the major release strategy is not entirely clear.

We could be even more generic with "a future major release". It was not so uncommon that we decided to keep a deprecated feature across majors, and in that case the message may be confusing.

I changed the deprecation notice to "This role will be removed in a future major release. Please use editor and viewer roles instead"

@elasticmachine update branch

@pugnascotia CI fails for this PR because it does not like the area label of deprecation. Existing ones are

But none of them seems to fit the deprecation here which is for a builtin role. What would be your recommendation? Thanks!

It's fine to add a new area to that last. Obviously we don't want lots and lots of areas, but if we need a another one then let's just add it. "Authorization" or "Security" would be OK, something like that.

I dropped this but this is still something I'd like to merge.

@pugnascotia Afaict I added "Authorization" in 72b1163. Still, I'm seeing a bunch of failures.

What's the suggested way forward?

@elasticmachine update branch

@sqren I updated the branch but there are formatting problems. To fix them, update your local branch checkout and run:

./gradlew spotlessApply

Then commit and push. I don't believe we have automation for this at present.