defaultNamespace field in config won't work on changing to other than default

[akankshakumari393]

Describe the bug
Botkube doesn't produce report of other namespace except default even if resource configuration is changed

To Reproduce
Steps to reproduce the behavior:

1. Go to 'resource_config.yaml'
2. Change the default namespace field other than default for ex- botkube
3. deploy botkube and then run the command @Botkube get deployments from the applications.
4. It will show results of default namespace instead of showing result for botkube namespace which is set to be default

Expected behavior
The result expected should be resources listed in botkube namespace

Screenshots

Results after deploying botkube

Additional context
If -n flag is provided then the response is correct

[sgandon]

Indeed I have also noticed it and fixed it in a PR I am preparing for #421 .

[alexavrutin]

I also encountered this problem but in my case adding -n didn't help. The bot simply does not return anything if I specify -n. If I don't specify -n, it returns "No resources found..." Any ideas what might cause it?

[sgandon]

@alexavrutin to be sure about what you are doing, the -n shall be used to specify a namespace like @botkube get pods -n default where default is the namespace named default.
You can just use -n without any string following it.

[ghost]

#458

[PrasadG193]

Fixed with: #459