Global variable to disable all endpoint pipes

Answered

Follow

Håkon Mellbye

• November 24, 2021 10:27

When running configs on dev-nodes or CI we currently have
task_manager”: {
    “disable_user_pipes”: true
  }
This breaks signaling when running on the dev node, so we have to do a full sesam-run from the CLI wich takes a lot of time. 
If we could have a global.disable_endpoints, we could only disable the endpoints but signaling would still work, making it better for development use. 

1

• Official comment

  

  Geir Ove Grønmo

  • February 07, 2022 09:27

  The sesam-py tool has not been designed to be run exclusively on a subscription. You should not have pipes on the subscription that are not managed by the sesam-py. sesam-py will disable the scheduler and run pipes itself.

  Comment actions Permalink
• 

  endre.bronnum

  • November 24, 2021 11:19

  I like Håkon's idea

  0

  Comment actions Permalink
• 

  Håkon Mellbye

  • February 07, 2022 10:02

  Not sure if I quite understand your response Geir Ove Grønmo. To clarify my goal of disabling endpoints is to be able to run the sesam-py tool once (sesam test command) and then be able to modify embedded data or add new config and make that change flow trough any connected pipes. Then after making the config changes I want to be able to run the sesam update command to update the expected files whiteout going to a full sesam run/test. In short I want to avoid having to do a new sesam run after updating/creating a pipe. Making the issue with sesam test being slow much more bearable. 

  0

  Comment actions Permalink
• 

  Geir Ove Grønmo

  • February 07, 2022 13:06

  Note that there is a sesam-py command line option that you can use to keep the user pipes enabled: -enable-user-pipes

   

  0

  Comment actions Permalink

Please sign in to leave a comment.