PostgreSQL technology: conditional hint for Azure targets #977
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agoncal
approved these changes
May 31, 2023
|
Tested successfully. |
|
@PhilipCattanach sorry about that, but this PR was not to be merged. With @mrizzi we are trying something different where we could overrid rules. See Azure/appcat-rulesets#47 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Alternative implementation for Azure/appcat-rulesets#39
When an Azure related targets is selected a further hint is added to the analysis with SPs and Category.
The classification is still there since it's just an information with 0 SP so it doesn't affect the effort involved in migrating.
Sample of analysis without and with a Azure target:
@agoncal WDYT?