Merge pull request #1667 from JoeStech/system_message_note

system message testing note in the RAG Copilot Extension LP

Author: jasonrandrews

content/learning-paths/servers-and-cloud-computing/copilot-extension/4-flask.md

@@ -147,6 +147,10 @@ system_message = [{
 }]
 ```
 
+{{% notice Note %}}
+You'll notice that system_message is lowercase, compared to the uppercase SYSTEM_MESSAGE above. This is because the [agent_flow](https://github.com/ArmDeveloperEcosystem/python-rag-extension/blob/main/utils/agent_functions.py#L28) function where this code resides defines system_message as a parameter, so that if you want to write a test harness to dynamically test many different system prompts you can.
+{{% /notice %}}
+
 Once the system message is built, add it to the original message to create `full_prompt_messages` and invoke the copilot endpoint:
 
 ```Python
@@ -229,4 +233,4 @@ GitHub recommends payload validation for the messages received from GitHub, to e
 
 In the python-rag-extension example repo, Arm has included a payload validation module to show you how to perform this validation. The file where this is implemented is [payload_validation.py](https://github.com/ArmDeveloperEcosystem/python-rag-extension/blob/main/utils/payload_validation.py).
 
-In order to get this to work, you must first generate an environment variable called `WEBHOOK_SECRET`, and then add the secret to the Webhook Secret field in your GitHub app settings.
+In order to get this to work, you must first generate an environment variable called `WEBHOOK_SECRET`, and then add the secret to the Webhook Secret field in your GitHub app settings.