Added Linter rule for BillingData property presence in resource's property bag.#850
Open
vayada wants to merge 1 commit into
Open
Added Linter rule for BillingData property presence in resource's property bag.#850vayada wants to merge 1 commit into
vayada wants to merge 1 commit into
Conversation
vayada
requested review from
AkhilaIlla,
danieljurek,
mikeharder,
raosuhas,
tejaswiMinnu and
weshaggard
as code owners
Author
|
I don't have required permissions to add label on this PR which is causing one merge validation failure for missing label. Can someone from maintainer of this repo add following label on this PR. test-BillingDataInPropertiesBag |
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
2 participants
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.
Added a new linter rule to enforce the presence of the BillingData property within a resource's property bag.
The BillingData property name is reserved for RP Platform billing integration functionality and is being standardized through Common Types.
To mitigate the risk of unexpected validation failures in production, the rule has initially been introduced as a staging rule (staging=true).
After the rule has successfully baked in with the staging flag for approximately 1–2 weeks and no regressions or compatibility issues are identified, it will be promoted to a production rule by setting staging=false.