Update how the broadcast name is handled to allow for greater user customization:
|
broadcast_title = f"{workflow_name} stream @AC {cam_name}, {formatted_time}" |
Doesn't matter so much immediately since these are only deployed within AC context, but will be necessary as others begin to implement. In particular, it's just the @AC that's problematic in this case. The rest can remain.
We could also probably remove this placeholder and instead suggest people to update the WORKFLOW_NAME from https://github.com/AccelerationConsortium/ac-training-lab/blob/main/src/ac_training_lab/picam/my_secrets_example.py as they see fit (e.g., appending the @ [organization] by themselves.
See AccelerationConsortium/ac-dev-lab#432
Likewise see AccelerationConsortium/ac-dev-lab#282
Update how the broadcast name is handled to allow for greater user customization:
streamingLambda/chalicelib/ytb_api_utils.py
Line 100 in 32e1ce8
Doesn't matter so much immediately since these are only deployed within AC context, but will be necessary as others begin to implement. In particular, it's just the
@ACthat's problematic in this case. The rest can remain.We could also probably remove this placeholder and instead suggest people to update the
WORKFLOW_NAMEfrom https://github.com/AccelerationConsortium/ac-training-lab/blob/main/src/ac_training_lab/picam/my_secrets_example.py as they see fit (e.g., appending the@ [organization]by themselves.See AccelerationConsortium/ac-dev-lab#432
Likewise see AccelerationConsortium/ac-dev-lab#282