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
With the addition of layered dynamic bundle configuration, command execution can be customized based on which user is executing the command, and what chat room they do it from. The API and cogctl can both be used to manipulate individual configuration layers, but there is manual work to be done if you want to get a sense of the command execution environment in effect for a specific room / user combination.
It would be nice to have a cogctl dynamic-command effective command to fill this gap, allowing administrators to be able to troubleshoot configuration-related issues. Specifying the bundle and optional --room and --user arguments would display the appropriately merged configuration.
It would be a good idea to implement this merging logic in Cog and expose it to cogctl via a new API endpoint. Relay already implements this merging logic internally when running in non-managed dynamic configuration mode, but cogctl shouldn't be the place to implement it; it should just straightforwardly consume the API.
We can display the output as plain YAML by default, but having an output option (maybe --as-env-vars?) would be nice, allowing users to run
With the addition of layered dynamic bundle configuration, command execution can be customized based on which user is executing the command, and what chat room they do it from. The API and
cogctl
can both be used to manipulate individual configuration layers, but there is manual work to be done if you want to get a sense of the command execution environment in effect for a specific room / user combination.It would be nice to have a
cogctl dynamic-command effective
command to fill this gap, allowing administrators to be able to troubleshoot configuration-related issues. Specifying the bundle and optional--room
and--user
arguments would display the appropriately merged configuration.It would be a good idea to implement this merging logic in Cog and expose it to
cogctl
via a new API endpoint. Relay already implements this merging logic internally when running in non-managed dynamic configuration mode, butcogctl
shouldn't be the place to implement it; it should just straightforwardly consume the API.We can display the output as plain YAML by default, but having an output option (maybe
--as-env-vars
?) would be nice, allowing users to runto help with debugging.
The text was updated successfully, but these errors were encountered: