关于LUIS与QNA Maker持续集成（版本控制）支持的问询

Hey there! Let's break down your questions about version control and CI/CD workflows for staging-to-production environments with LUIS and QnA Maker:

Current Capabilities #

LUIS #

LUIS already has robust version control and CI/CD support to streamline your environment transitions:

• You can create distinct versions of your LUIS app (e.g., dev, staging, prod) directly in the portal or via API, keeping changes isolated across environments.
• Automate deployments using Azure DevOps' LUIS extension, or build custom pipelines with the LUIS REST API to push updates seamlessly from dev to staging to production.
• Export your LUIS model as JSON files and store them in Git (or any version control system) to track every change, roll back if needed, and collaborate with your team effectively.

QnA Maker #

QnA Maker also offers full version control and CI/CD capabilities tailored to your staging workflow needs:

• Create and manage multiple versions of your knowledge base (KB) to test changes in a staging environment before rolling out to production.
• Use the QnA Maker API or Azure DevOps tools to automate KB publishing and environment migrations—no manual steps required for your staging-to-prod flow.
• Export your KB as .qna or JSON files to include in your version control repo, so you can track content updates alongside your codebase.

Roadmap & Future Plans #

Microsoft doesn't publicly share exact, detailed roadmaps for these services, but the team is constantly iterating on CI/CD and version control features based on user feedback. If you have specific needs (like tighter Git integration or simplified pipeline templates), submitting your suggestions through Azure's feedback channels helps shape future updates.

内容的提问来源于stack exchange，提问作者Vinay Jayaram