You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I could not see any configuration about default namespace to work with kubectl commands. So every time passing ns parameter is so verbose.
Describe the solution you'd like
It would be great to add namespace parameter to settings field in config.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Feature Pull Request
##### SUMMARY
<!--- Describe the change, including rationale and design decisions -->
This Commit,
- Adds `kubectl.Enabled`, `Kubectl.DefaultNamespace` to `Config.Settings` to configure default namespace, under which all botkube kubectl commands will be executed by default.
- changes `Settings.RestrictAccess` into `Settings. Kubectl.RestrictAccess`
- updates all config.yaml files
<!---
If you are fixing an existing issue, please include "Fixes #nnn" in your
PR comment; and describe briefly what the change does.
-->
<!--- Please list dependencies added with your change also -->
Fixes#176
**Preview**:
```yaml
settings:
# Kubectl executor configs
kubectl:
# Set true to enable kubectl commands execution
enabled: false
# set Namespace to execute botkube kubectl commands by default
defaultNamespace: default
# Set true to enable commands execution from configured channel only
restrictAccess: false
```
Is your feature request related to a problem? Please describe.
I could not see any configuration about default namespace to work with kubectl commands. So every time passing ns parameter is so verbose.
Describe the solution you'd like
It would be great to add namespace parameter to settings field in config.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: