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
Send all the command results visible only to person triggering the command (currently it is visible to the whole channel). Ideally this could be configurable in admin section / plugin configuration (in order not to the change your design concept entirely and keep the ability to choose)?
It would be useful if this would / could influence also other relevant nautobot chatops integrations (IP Fabric, Grafana etc.)
Use Case
The channel is getting easily messy with several command outputs from different team members therefore it is hard to orient in such a channel + also people do not tend to search for older messages but rather type their own.
Also the data that were provided, let's say yesterday, doesn't have to be still valid and person is sending command again anyway because one want to be certain about up-to-date data.
The text was updated successfully, but these errors were encountered:
@smk4664 / @glennmatthews as I'm looking at a potential implementation of this. I think we can apply this via a setting within the dispatchers instead of a per chat command (my original plan of attack). I think this would be helpful for having a global setting capability. I'm trying to think if there may be some short comings to implementing it this way or not. Either way I think it gets to having a setting, which defaults to False.
Environment
Proposed Functionality
Send all the command results visible only to person triggering the command (currently it is visible to the whole channel). Ideally this could be configurable in admin section / plugin configuration (in order not to the change your design concept entirely and keep the ability to choose)?
It would be useful if this would / could influence also other relevant nautobot chatops integrations (IP Fabric, Grafana etc.)
Use Case
The channel is getting easily messy with several command outputs from different team members therefore it is hard to orient in such a channel + also people do not tend to search for older messages but rather type their own.
Also the data that were provided, let's say yesterday, doesn't have to be still valid and person is sending command again anyway because one want to be certain about up-to-date data.
The text was updated successfully, but these errors were encountered: