Test on SOAR with the new Python 3.13 SOAR Automation Broker

[edthedev]

Context

Update in #61 and #63.

We have kicked off a request for a new local automation broker that defaults Python to version 3.13.

Once that is available, we should re-test to verify the app updates for Python 3.13 we successful.

Tasks

• request a new Python 3.13 SOAR automation broker
• (blocker / in progress) new automation broker host created
• (blocker) new automation broker host setup
• ensure we have a successfully installed Test Null Router SOAR app recognized as Python 3.13
• connect the new Python 3.13 broker to an asset configured for the Python 3.13 Test Null Router
• run test_connectivity the same way in the production null router with the same automation broker
• no current test endpoint - discuss at stand-up
• no current test endpoint - discuss with wider automation group
• we can also safely do a test_connectivity with the production asset
• is there a safe target for a production 'block'? Yes. We could test by re-blocking something that is already recently blocked anyway. We can ask an incident responder for an example IP.
• verify test_connectivity succeeds in the Null Router test app through an updated broker
• verify block function succeeds in the Null Router test app through the new broker, with an already blocked IP an incident responder

[edthedev]

Python 3.13 version deployed successfully to test, recognized at Python 3.13.

[edthedev]

To verify this, we will need a test playbook, as the issue with SOAR not routing to the expected broker from the edit screen results in a time-out.

Edit: It is also possible to test on the edit screen for the configured asset.

[edthedev]

Marked as blocker as this blocks our update to Python 3.13.

[edthedev]

Interesting, our Test BHR app fails Test_Connectivity on both automation brokers, right now.

Automation Broker 4 is 'Active'.
Sending command to execute 'test connectivity' on Automation Broker 'soarauto2'.
Loaded action execution configuration
Connecting to endpoint
2 actions failed 

[edthedev]

Still failing today, so not just a network hiccup.

[edthedev]

We have two configured production assets for Null Router. One works, one fails.

It has been awhile since we updated this and kicked the test tires.
I think we need to reach out to the engineers and see if they have new settings for testing.

[edthedev]

Per chat with SA in engineering today, the old test endpoint has, indeed been decommissioned; and a new test endpoint has not been established yet. Let's discuss at a stand-up and then at the larger weekly automation meeting.