feat(discoveryengine): add action, BAP, and destination config support to google_discovery_engine_data_connector#16290
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Hello! I am a robot. Tests will require approval from a repository maintainer to run. Googlers: For automatic test runs see go/terraform-auto-test-runs. @trodge, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
2b0006a to
51c9466
Compare
|
This PR is necessary in order to support Gemini Enterprise's new way of handling Actions (write operations). It is my first PR into this repository, so I'm open to any suggestions and willing to do whatever is necessary to get it over the finish line. Thank you! This is the payload that the API expects: |
… `google_discovery_engine_data_connector`
Adds new API surface to support the ACTIONS connector mode:
- `action_config` block with:
- `action_params` (KeyValuePairs, ignore_read) — credentials and
configuration for the action connector
- `is_action_configured` (computed) — whether the action connector
is fully configured
- `create_bap_connection` (bool, ignore_read) — whether to create
a BAP connection
- `bap_config` block with:
- `enabled_actions` (list of strings) — which actions to enable,
e.g. create_issue, update_issue, change_issue_status
- `supported_connector_modes` (list of strings) — connector modes
for the BAP configuration, e.g. ACTIONS
Also adds:
- Jira example template demonstrating action_config and bap_config
- Updated state migration v0 schema for compatibility
- Updated acceptance tests with action_config and bap_config coverage
action_config block to google_discovery_engine_data_connectorgoogle_discovery_engine_data_connector
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 39 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
| ImportState: true, | ||
| ImportStateVerify: true, | ||
| ImportStateVerifyIgnore: []string{"collection_display_name", "collection_id", "location", "params"}, | ||
| ImportStateVerifyIgnore: []string{"collection_display_name", "collection_id", "location", "params", "action_config.0.action_params", "action_config.0.create_bap_connection"}, |
There was a problem hiding this comment.
Looks like you'll need to add update_time here.
There was a problem hiding this comment.
@trodge Thank you. I've added it. Also, I can't view the ErrorMessage or DebugLog above, getting a 403 Forbidden, so hands feel a bit tied in helping debug these.
Does this repo require you to manually trigger the additional test suites each time?
4bfe9d0 to
596f9f9
Compare
|
@modular-magician /test |
|
@trodge This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
/gcbrun |
|
Test is still failing with |
|
@GoogleCloudPlatform/terraform-team @trodge This PR has been waiting for review for 1 week. Please take a look! Use the label |
|
/gcbrun |
|
Thanks @trodge, I've updated the code to fix the latest issues in question. |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_discovery_engine_data_connector" "primary" {
entities {
key_property_mappings = # value needed
}
}
|
Tests analyticsTotal tests: 39 Click here to see the affected service packages
🟢 All tests passed! View the build log |
…figs` to data connector Adds two missing fields to `google_discovery_engine_data_connector`: - `data_source_version` (integer) — specifies the version of the data source, e.g. 3 for Jira v3 - `destination_configs` (nested array) — configures where data is served, with each entry containing a `key` and a list of `destinations` with a `host` field
|
@trodge I've got all tests passing now, if you can please take a look. Thank you! |
This has been addressed. |
|
@GoogleCloudPlatform/terraform-team @trodge This PR has been waiting for review for 2 weeks. Please take a look! Use the label |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 39 Click here to see the affected service packages
🟢 All tests passed! View the build log |
|
@GoogleCloudPlatform/terraform-team @trodge This PR has been waiting for review for 3 weeks. Please take a look! Use the label |
bb1e568
…t to `google_discovery_engine_data_connector` (GoogleCloudPlatform#16290)
…t to `google_discovery_engine_data_connector` (GoogleCloudPlatform#16290)
…t to `google_discovery_engine_data_connector` (GoogleCloudPlatform#16290)
Adds the missing API surface for Gemini Enterprise / Agentspace data connectors to
google_discovery_engine_data_connector, enabling full configuration of action connectors, BAP settings, destination routing, and data source versioning.New fields
action_configblockConfigures action capabilities for connectors using the
ACTIONSconnector mode (e.g. Jira actions).action_params(map, write-only) — connection credentials and configuration (instance URI, client ID, client secret, auth type)is_action_configured(bool, computed) — whether the action connector is fully configuredcreate_bap_connection(bool, write-only) — whether to create a BAP connectionbap_configblockControls which actions are enabled for connectors using the
ACTIONSconnector mode.enabled_actions(list of strings) — actions to enable, e.g.create_issue,update_issue,change_issue_status,create_comment,update_comment,upload_attachmentsupported_connector_modes(list of strings) — connector modes for the BAP configuration, e.g.ACTIONSdestination_configsblockConfigures where data is served for the connector.
key(string) — destination config key, e.g.urldestinations— list of destination objects, each with ahost(string)data_source_version(integer)Specifies the version of the data source, e.g.
3for Jira v3.Example usage
Changes
mmv1/products/discoveryengine/DataConnector.yaml— addedactionConfig,bapConfig,destinationConfigs, anddataSourceVersionproperty definitionsmmv1/templates/terraform/examples/discoveryengine_dataconnector_jira_with_actions.tf.tmpl— new Jira example demonstrating all new fieldsmmv1/templates/terraform/state_migrations/discovery_engine_data_connector.go.tmpl— added new fields to v0 schema for state migration compatibilitymmv1/third_party/terraform/services/discoveryengine/resource_discovery_engine_data_connector_test.go— updated acceptance tests with all new fields