chore: update provider schema and issue templates #2464
Conversation
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
terraform-provider-grafana
bot
requested a review
from a team
as a code owner
Contributor
|
In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically. |
terraform-provider-grafana
bot
force-pushed
the
automated/update-schema
branch
2 times, most recently
from
1f16a8e to
887a327
Compare
Auto-generated by schema consistency workflow
terraform-provider-grafana
bot
force-pushed
the
automated/update-schema
branch
from
887a327 to
b2a5573
Compare
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.
Automated Schema Update
This PR was automatically created because recent changes to the codebase affected the Terraform provider schema.
Changes Made:
provider_schema.jsonwith latest schema definitions.github/ISSUE_TEMPLATE/3-bug-report-enhanced.ymlwith new schema optionsTriggered By:
Add a ListCollectors cache to the collectorResource
Cache is reset after performing a mutating action or an Import
🤖 This PR was created automatically by the schema consistency workflow. Please review the changes before merging.