Thanks for the clarification on the devstack.yml file.
Ok I see! Since it is was YAML file I thought it would require YAML formatting. I tried with python formatting and indeed there is no error.
Actually I realised that both the YAML and python plugin work correctly since I noticed that the file /home/ubuntu/.local/share/tutor/env/apps/openedx/settings/lms/production.py was updated with the code
XBLOCK_SETTINGS["lti_consumer"] = {
"parameter_processors": [
"tahoe_lti.processors:basic_user_info",
"tahoe_lti.processors:personal_user_info",
"tahoe_lti.processors:cohort_info",
"tahoe_lti.processors:team_info",
]
}
when any of the 2 plugins (python or yaml) is enabled. I also noticed that the same piece of code is present in the files /openedx/edx-platform/lms/envs/tutor/production.py and /openedx/edx-platform/cms/envs/tutor/production.py of both contianer tutor_local_lms_1 and tutor_local_cms_1 when any of the two plugins (python or yaml) is enabled. So in the end I think both the Xblock installation of Tahoe LTI Customizations and the plugin installation work (python or yaml, same effect). But it does not seem to have any effect on the parameters that are sent by edX to the LTI tool (according to LTI Tool Provider emulator) which is the purpose of Tahoe Customizations (in particular sending the user data to obtain the name of the user). I do not know where the problem is coming from but I am thinking that it has nothing to do with Tutor so I will try to post the issue on the edX forum.