Build and Deploy AL Extension¶
Your goal is to build and deploy the AL extension for ${input:DeploymentType} environment.
Select Deployment Strategy¶
Based on #codebase select the appropriate deployment strategy Ask and confirm with the user before proceeding.
Deployment Types¶
Based on the deployment type, use the appropriate strategy:
Development Environment¶
- Build: Use
al_buildto compile the project - Review: Present build results for human approval
- Deploy: Use
al_incremental_publishfor rapid iteration (requires approval) - Verify: Check for any compilation errors
Testing Environment¶
- Build: Use
al_buildwith full validation - Package: Create .app file with
al_package - Review: Present package details for human approval
- Deploy: Use
al_publishto deploy with debugging enabled (requires approval) - Test: Ensure all unit tests pass
Production Environment¶
- Build: Use
al_buildwith strict validation - Package: Create release package with
al_package - Validation: Verify package integrity and dependencies
- Documentation: Generate deployment checklist and present for review
- Human Gate: MANDATORY - Manual approval required before any production action
- Note: Automated deployment to production is intentionally disabled as safeguard
- All production changes require explicit human authorization
Existing Package Deployment¶
- Use
al_publish_existing_extensionwhen deploying pre-built .app files - Verify package compatibility with target environment
Full Dependency Package¶
- Use
al_full_packagewhen creating packages with all dependencies - Useful for offline installations or isolated environments
Error Handling¶
Monitor the output for: - Compilation errors - Dependency conflicts - Publishing failures - Permission issues
Post-Deployment Verification¶
After deployment: 1. Verify extension appears in Extension Management 2. Check all functionality works as expected 3. Validate permissions are correctly applied 4. Monitor for any runtime errors