Enforcing Global Context — Take 2

Explicitly telling Amazon Q to validate an application against global context to write code that matches desired standards

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

⚙️ Security Automation (Pre-AI). The Code.

⚙️ AI Automation. The Code.

🔒 Related Stories: Cybersecurity | Penetration Tests

💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I wrote another story about adding information to a readme to get Q to follow certain standards but it didn’t work really well. Also I don’t want to repeat that context in every repository.

What I did (an idea from a video I watched from Daniel Meissler plus my own experience and thoughts) is to create myself a repository for my global context.

Then I explicitly add it to my context manually:

/context add [my global context file]

I have to do that each time unfortunately as explained in the last post. Maybe AWS will allow us to set that permanently in the future, or if it does, help Q find the correct answer because Q is telling me that is not possible. Or perhaps we will have a way to extend the default context.