Enhance sensitive field handling for BigQueryDataTransferConfig

[jingyih]

This is a tracking issue. We need to enhance the handling of sensitive fields for this resource. The GCP API field params is a map where the valid key names depend on the value of another field, dataSourceId, which specifies the type of transfer config. To address this, we likely need to introduce virtual KRM fields (strongly typed for each transfer configuration type) and implement proper handling for sensitive values within the map.

[jingyih]

/cc @yuwenma

I just realized I couldn’t find the beta promotion of BigQueryDataTransferConfig mentioned in any release notes. I believe it was promoted in version 1.125. Can we edit previously published release notes?

[yuwenma]

/cc @yuwenma

I just realized I couldn’t find the beta promotion of BigQueryDataTransferConfig mentioned in any release notes. I believe it was promoted in version 1.125. Can we edit previously published release notes?

Because we have a pending discussion on whether to special handle the sensitive fields. This could end up as API changes. Let's add the release note in 1.126 .