rule: adminUsername-should-not-be-literal #4702
Merged
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
| @@ -0,0 +1,49 @@ | |||
| # AdminUserName should not be a literal | |||
There was a problem hiding this comment.
@MarcusFelling Please review
There was a problem hiding this comment.
@mumian will we need to sync with you when adding new linter rules so you can add them to the new docs location?
There was a problem hiding this comment.
A new aka link has been generated https://aka.ms/bicep/linter/adminUsername-should-not-be-literal and points to https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/adminUsername-should-not-be-literal
src/Bicep.Core.UnitTests/Diagnostics/LinterRuleTests/LinterRuleTestsBase.cs
Show resolved
Hide resolved
eb3b624
to
4bab91f
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Fixes #3971
@MarcusFelling Example of the error message: