Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add deprecation notices for Security Plugin tools #503

Open
peternied opened this issue Apr 11, 2022 · 3 comments
Open

[FEATURE] Add deprecation notices for Security Plugin tools #503

peternied opened this issue Apr 11, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request v3.0.0

Comments

@peternied
Copy link
Member

peternied commented Apr 11, 2022

Is your feature request related to a problem?
In OpenSearch 3.0 several tools that are part of the security plugin will be replaced. We need to communicate to OpenSearch administrators that this change is happening.

What solution would you like?
We should put up a notice on the documentation page for security admin; however, we don't have a replacement in hand. The scope could be a little as updating the path of the existing tool, or a complete replacement with a new CLI. We don't have a firm plan in place for 3.0.0 so we need flexibility - and it would also be great to get feedback from the community on how they would like the tool(s) to be updated.

Do you have any additional context?

@peternied peternied added enhancement New feature or request untriaged labels Apr 11, 2022
@peternied peternied changed the title [FEATURE] Add deprecation notices for Security tools [FEATURE] Add deprecation notices for Security Plugin tools Apr 11, 2022
@kolchfa-aws
Copy link
Collaborator

@cwillum Could you investigate whether we should put a deprecation warning up now? Thanks.

@cwillum
Copy link
Contributor

cwillum commented Mar 3, 2023

@peternied After reviewing the PRs that are associated with this one, I've started forming an idea of what a notice of this kind should look like. The questions I have now are where and how broadly we want to display it, what to include as guidance for what admins can expect next, and in which version do we want to begin alerting the stakeholders. Do we want to recommend that admins take some action immediately? Let's discuss this when you have a chance.
@here

@peternied
Copy link
Member Author

I setup some time for a discussion - but lets make sure to circle back and put some of those thoughts here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v3.0.0
Projects
None yet
4 participants