-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Solution Checker for Managed Environments #116
Comments
Solution checker documentation: https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-solution-checker |
@eduardodfmex can you add more context/information? this looks only partially filled out |
@leighatami I add more description to this. |
The provider already allows you to basically enable or disabled the Automatic Solution Check, as per below.
This issue is about fine tuning the exact rules that the Solution Check will actually check, and there are lots of options, so it would be a lot of effort to create, test and document these, for what I think are very edge use-cases. Not sure it is worth the effort IMHO. |
Solution checker works with unmanaged solutions that can be exported from an environment. With the solution checker feature, you can perform a check within seconds on your solution, which uses a set of best practice rules to quickly identify problematic patterns. After the check completes, you receive a detailed report in Power Apps as well as in an email message that lists the issues identified, the components and code affected, and links to documentation that describes how to resolve each issue. |
Solution Checker for Managed environments
When converting an environment to managed, the "Solution checker enforcement" option allows us to enable tests when importing solutions into the managed environment.
Managed environments requires the configuration of Solution checker, You can use solution checker in Managed Environments to enforce rich static analysis checks on your solutions against a set of best practice rules and identify problematic patterns.
Solution Checker enforcement description
Automatically verify solution checker results for security and reliability issues before solution import. Learn more
Solution Checker ask for 3 kinds of enforcement:
• None, Turn off solution checker verification during solution import. You can continue to manually review the results in the solution explorer.
• Warm, Check for security and reliability issues in the solution checker results, but do not block solution import for any issues.
• Block, Check for security and reliability issues in the solution checker results and block the solution from being imported if critical issues are found.
Send emails only when a solution is blocked. If unchecked, you'll also get emails when there are warnings.
Rule exclusions / Excluded Rules
You can select to exclude solution checker rules from enforcement. For example, a particular rule might take significant time and effort to fix across the solution, but you would still like the rest of the rules to be enforced. Use the Excluded Rules dropdown list to select the rules to exclude from enforcement.
The list contains rule names and descriptions grouped by category and sorted by severity. As a reminder, only critical severity rules block a solution from being imported.
Excluded Rules for Managed Environments
Useful links:
Solution checker enforcement in Managed Environments - Power Platform | Microsoft Learn
Use solution checker to validate your solutions - Power Apps | Microsoft Learn
Resource
Potential Terraform Configuration
Definition of Done
make docs
Contributions
Do you plan to raise a PR to address this issue?
See the contributing guide for more information about what's expected for contributions.
The text was updated successfully, but these errors were encountered: