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

Provide an option to get only a part of Botkube configuration #892

Open
mszostok opened this issue Dec 15, 2022 · 0 comments
Open

Provide an option to get only a part of Botkube configuration #892

mszostok opened this issue Dec 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@mszostok
Copy link
Collaborator

Overview

We should allow getting only a part of Botkube configuration. We have at least two options:
-@Botkube config {name}

  • @Botkube config - returns configuration but in a context of a given channel.
  • @Botkube config --all - returns the whole (even data that is not connected with a given channel) Botkube configuration.
  • @Botkube config executors - returns executors configuration in a context of a given channel
  • @Botkube config actions -returns actions configuration in a context of a given channel
  • etc.
  • or supporting a more generic approach like @Botkube config --json-path={property_name} e.g. --json-path=communicators.slack (similar to what kubectl does)

Acceptance Criteria

  • provide an option to get only a part of Botkube configuration.
  • provide an option to get configuration in a context of a given channel (e..g. get configuration of all enabled executors in a given channel).
@mszostok mszostok added enhancement New feature or request needs-triage Relates to issues that should be refined labels Dec 15, 2022
@mszostok mszostok added this to Botkube Dec 15, 2022
@mszostok mszostok added this to the v0.18.0 milestone Dec 15, 2022
@pkosiec pkosiec removed this from the v0.18.0 milestone Jan 10, 2023
@pkosiec pkosiec moved this to Todo in Botkube Jan 10, 2023
@pkosiec pkosiec removed the needs-triage Relates to issues that should be refined label Feb 2, 2023
@pkosiec pkosiec removed the status in Botkube Mar 7, 2023
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
Status: No status
Development

No branches or pull requests

2 participants