fix(query): fixed results to mention correct resource type in secret without expiration date query#7954
Merged
Conversation
Contributor
This file contains hidden or 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
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.








Reason for Proposed Changes
Secret Without Expiration Datereturns a misleading result, stating that a resource of typeMicrosoft.Security/securityContactsshould haveattributes.expproperty id defined, but the resource that this query is tackling is actuallyMicrosoft.KeyVault/vaults/secretsProposed Changes
Microsoft.KeuVault/vaults/secrets.getKeyWithCurlyBracketsmethod, by adding a conditionlen(parts) >= valuePartsLengthbefore accessing parts[len(parts)-2] and parts[len(parts)-1] to prevent potential index out of bounds errorsI submit this contribution under the Apache-2.0 license.