Add a linter to warn on nondeterministic resource names #7491
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
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.
Resolves #7562
One theme that came up during discussion around #6065 was that while you certainly can create a resource that can't be addressed outside of its initial deployment context, doing so nerfs WhatIf, makes deployments non-repeatable, and is generally not a great idea.
This PR adds a linter that will emit a warning if any of a resource's unique identifiers rely on a non-deterministic value (i.e., a parameter whose default value uses the
newGuidorutcNowfunctions). This does not address the core issue of #6065 but should help with one of the concerns around the "outlining" solution proposed in that issue.Microsoft Reviewers: Open in CodeFlow