Fix connection schema field not saved for providers without field behaviour

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test

[kaxil]

Fixes the connection form's schema field being silently lost for providers that don't define get_ui_field_behaviour() (Oracle, and many others).

• On create: schema was never sent in the request, so it was stored as None and get_uri was malformed (missing /{schema} path segment)
• On edit: the stray url_schema key in the request body triggered a 422 from StrictBaseModel(extra="forbid")

Root cause

convertStandardFields in useConnectionTypeMeta.ts has two branches:

apiFields	Key in returned dict	Correct?
non-null	schema (remapped from url_schema)	Yes
null (no field behaviour)	url_schema (raw default key)	No

ConnectionStandardFields.tsx iterates the keys and creates a react-hook-form Controller with name={key}. When the key was url_schema instead of schema, user input went to a phantom field -- the real schema stayed at its default "", which useAddConnection.ts converted to undefined (omitted from the request).

On edit, useEditConnection.tsx spreads ...requestBody which included the rogue url_schema key, and the backend's ConnectionBody(extra="forbid") rejected it.

Fix

Remap url_schema to schema in the null branch, matching the non-null path:

if(apiFields===null){const{url_schema: urlSchema, ...rest}=defaultFields;return{ ...rest,schema: urlSchema??{}};}

Affects every provider without get_ui_field_behaviour(). Oracle is the reporter, but the bug applied generically.

Closes: #65257

[Copilot]

Pull request overview

Fixes the Connections UI so the Schema field is correctly wired for providers that do not implement get_ui_field_behaviour() (i.e., when standard_fields metadata is null), preventing schema from being dropped on create and preventing url_schema from being sent (and rejected) on edit.

Changes:

• Remaps url_schema → schema in convertStandardFields() when apiFields === null, matching the behavior of the non-null branch.
• Ensures the generated standard_fields keys align with the ConnectionBody form field names (schema), so react-hook-form binds user input to the correct field.

[github-actions]

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-2-test