`WORKFLOW_NAME` for AWS Lambda function for streaming can't be identical

[sgbaird]

I probably forgot an earlier conversation, but it seems that issues are caused if WORKFLOW_NAME is identical to another device, even if CAMERA_NAME is unique. This occurred when I set up several streams called [undecided]-[undecided]-SDLT

If we implement #271, it will hopefully be easier to have visibility since the lambda code will be hosted on GitHub.

Likewise, we should update the my_secrets_example.py with a comment about both the character limit (making sure to subtract what gets appended by default in the AWS Lambda function, or just generally encouraging shorter workflow names) and that WORKFLOW_NAME should be unique.

[Neil-YL]

I see.

It is because the end stream function is using the workflow name to end stream and the playlist name doesn't involve with the camera id either, so previous [undecided]-[undecided]-SDLT will be ended and all [undecided]-[undecided]-SDLT will be listed in a same playlist.

def end_active_broadcasts_for_device(workflow_name: str):
    broadcasts_list = list_broadcasts("active")

    for broadcast in broadcasts_list:
        title = broadcast["snippet"]["title"]
        life_cycle_status = broadcast["status"]["lifeCycleStatus"]
        if workflow_name.lower() in title.lower() and life_cycle_status in ("live", "testing"):
            broadcast_id = broadcast["id"]
            print(f"Ending broadcast: {broadcast_id} | Title: {title} | Status: {life_cycle_status}")
            YOUTUBE.liveBroadcasts().transition(
                broadcastStatus="complete",
                id=broadcast_id,
                part="status"
            ).execute()

[Neil-YL]

I think we should mention that the combination of [device]-[workflow]-[SDL-num] should not be the same with any previous stream. Since we have the SDL-num in it, the SDL could decide how to manage the first two items within their SDL.

But we need to decide what WOFLOW_NAME should be (for testing purpose?) in our current preparation stage.
We don't want to flood our ytb channel with so many random generated playlist as well.

[sgbaird]

Good points. As a temporary measure, instead of SDLT I used the four characters from the camera. Like you said, this leads to additional playlists (and good point about the playlists not having the camera ID in them). When they had the same workflow names, it was hard to keep all three streams up. Everything seemed OK after switching to unique names.

[Neil-YL]

Ideally, for long-term monitoring, we want to keep the same workflow within the same playlist, even if we swap out different cameras. So I decided not to include the camera ID in the playlist name.

[sgbaird]

I see where you're coming from. Making a comment in my_secrets_example.py seems sufficient for now. Later if we keep running into issues we can consider adding camera ID into playlist name.

[sgbaird]

Instructions for copilot: add a clarifying comment to the example secrets file under the src/ac_training_lab/picam directory.