I just pushed an updated version of the CLI. I'd like to raise two issues;
First; Right now publish method does not allow extra arguments.
While this might be the desired use. I think it should not fail to publish, rather
either mark the extra columns and publish, or
split these columns, publish the fixed template part, and report back the extra fields to the user.
Manipulations in the publish class can be made see here
Second, I think the snews_pt is meant for users to interact with the system without having to deal with any backend tools. The publishing tools are already nice and usable, however, we should also carry the means to subscribe to alert channel, and I think this subscription should also allow downloading the received alerts in json or some other format. I don't think users would monitor the terminal all the time.
I also would like to suggest starting using python config files for broker, channel, token, etc (basically replacing the env file). This way later, we can either ask users to put their experiments once in the config file or try to fetch it from hop.auth. I can work on that if agreed.
I just pushed an updated version of the CLI. I'd like to raise two issues;
First; Right now publish method does not allow extra arguments. While this might be the desired use. I think it should not fail to publish, rather
Second, I think the snews_pt is meant for users to interact with the system without having to deal with any backend tools. The publishing tools are already nice and usable, however, we should also carry the means to subscribe to alert channel, and I think this subscription should also allow downloading the received alerts in json or some other format. I don't think users would monitor the terminal all the time.
I also would like to suggest starting using python config files for broker, channel, token, etc (basically replacing the env file). This way later, we can either ask users to put their experiments once in the config file or try to fetch it from
hop.auth
. I can work on that if agreed.