mirror of
https://github.com/microsoft/terraform-provider-fabric.git
synced 2026-11-04 12:02:31 +00:00
e08c7a0ac9
# 📥 Pull Request ## ❓ What are you trying to address - Many resource examples set `processing_mode = "parameters"` (lowercase). The `processing_mode` attribute is validated with a case-sensitive `stringvalidator.OneOf("GoTemplate", "None", "Parameters")` (`internal/pkg/fabricitem/resource_schema.go`, values from `internal/pkg/transforms/payload.go`). As a result, a user who copies these examples gets a validation error. - The value comes from the itemgen example template, so every newly scaffolded resource inherited it. - Flagged during review of #1134 and deferred to this repo-wide fix. No tracking issue exists. ## ✨ Description of new changes - Changed `processing_mode = "parameters"` to `"Parameters"` in 22 `examples/resources/*/resource.tf` files: activator, apache_airflow_job, copy_job, data_pipeline, dataflow, digital_twin_builder, eventhouse, eventstream, kql_dashboard, kql_database, kql_queryset, mirrored_azure_databricks_catalog, mirrored_database, mounted_data_factory, notebook, org_app, paginated_report, report, semantic_model, spark_job_definition, user_data_function, variable_library. - Made the same fix in `tools/itemgen/templates/examples/resource.tf.tmpl` so new resources start with the correct value. - Regenerated `docs/` with `task docs`; the 22 corresponding pages changed. - Every changed line is a `processing_mode` line; there are no functional or schema changes. A repo-wide search found no other casing problems (`gotemplate`/`none`) in examples, templates, tests or `.github/`. - Added a `documentation` changelog entry (`.changes/unreleased/documentation-20261104-133706.yaml`). **Validation** - `task docs`: passed (docs regenerated, markdownlint reported 0 issues) - `task lint:tf`: passed - `git grep 'processing_mode = "parameters"'`: no matches remain ## ☑️ PR Checklist - [ ] Link to the issue you are addressing is included above (N/A: no tracking issue; originates from #1134 review) - [x] Ensure the PR description clearly describes the feature you're adding and any known limitations ## ☑️ Resources / Data Sources Checklist PRs for new/enhanced resources or data sources are expected to meet the following criteria: - [ ] Production quality implementation of the resource or data-source in [./internal/services](./internal/services) (N/A) - [ ] Unit Tests and Acceptance Tests for your contribution in [./internal/services/<service_name>](./internal/services) (N/A) - [ ] Tests should pass and provide >80% coverage of your contribution (N/A) - [x] Examples for your contribution in [./examples](./examples) (see [Terraform Documentation on examples](https://developer.hashicorp.com/terraform/tutorials/providers-plugin-framework/providers-plugin-framework-documentation-generation#add-configuration-examples)) - [ ] [Schema descriptions](https://developer.hashicorp.com/terraform/tutorials/providers-plugin-framework/providers-plugin-framework-documentation-generation#add-schema-descriptions) for your resource or data-source in [./internal/services](./internal/services) (N/A) - [ ] Docs templates in [./templates](./templates) (N/A) - [x] Updated auto-generated documentation in [./docs](./docs). (DO NOT manually edit [./docs](./docs) - your updates will be overwritten) --------- Co-authored-by: Sabre Ammar <saammar@microsoft.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>