The GitHub Actions job "Required Checks" on texera.git/main has failed. Run started by GitHub user github-merge-queue[bot] (triggered by github-merge-queue[bot]).
Head commit for run: 3dcd82b8e1602e3fa44b5121f09c9cb2c8d3b86b / Prateek Ganigi <[email protected]> fix(workflow-operator): mask the HF API token field as a password widget (#7215) ### What changes were proposed in this PR? The HuggingFace inference operator's `hfApiToken` field was a plain text input, the token was visible in the property panel and stored verbatim in the workflow JSON. This adds `@JsonSchemaInject(json = UIWidget.UIWidgetPassword)` to the field so it renders as a masked password input, following the same convention the SQL source operators (`SQLSourceOpDesc`) already use for their password field. ### Any related issues, documentation, discussions? Closes #7193. ### How was this PR tested? `sbt "WorkflowOperator/testOnly org.apache.texera.amber.operator.huggingFace.* org.apache.texera.amber.operator.metadata.*"`: the Hugging Face suite and the operator-metadata specs pass (146 tests). This includes a new test asserting the generated JSON schema marks `hfApiToken` as a password widget (`widget.formlyConfig.templateOptions.type == "password"`), and the `metadata.*` specs confirm operator-schema generation still succeeds. scalafmt clean. The password widget is a schema-only change reusing an existing, shipped mechanism (`UIWidget.UIWidgetPassword`, already used by the SQL source operators), so no UI change was needed. ### Was this PR authored or co-authored using generative AI tooling? Yes, this PR was co-authored with Claude Opus 4.8 in compliance with ASF. Report URL: https://github.com/apache/texera/actions/runs/30773835553 With regards, GitHub Actions via GitBox
