support gemini-usage connector
#858
Conversation
There was a problem hiding this comment.
PR Overview
This PR adds an initial version of the Gemini Usage connector documentation to guide users through setup and usage.
- Added a new README file with details about downloading and processing Gemini Usage reports.
- Provided step‐by‐step instructions to configure the connector via Terraform.
Reviewed Changes
| File | Description |
|---|---|
| docs/sources/google-workspace/gemini-usage/README.md | New documentation for the Gemini Usage connector detailing setup and usage instructions |
Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.
| 5. Create the a `gemini-usage` connection in Worklytics; see `TODO 3 - gemini-usage` file that your `terraform apply` generated. | ||
|
|
There was a problem hiding this comment.
[nitpick] There is a duplicate article 'the a' in the instruction. Please modify it to either 'Create a gemini-usage connection...' or 'Create the gemini-usage connection...'.
| 5. Create the a `gemini-usage` connection in Worklytics; see `TODO 3 - gemini-usage` file that your `terraform apply` generated. | |
| 5. Create a `gemini-usage` connection in Worklytics; see `TODO 3 - gemini-usage` file that your `terraform apply` generated. |
Copilot is powered by AI, so mistakes are possible. Review output carefully before use.
| @@ -214,6 +214,7 @@ module "bulk_connector" { | |||
| bucket_write_role_id = module.psoxy.bucket_write_role_id | |||
| secret_bindings = module.psoxy.secrets | |||
| example_file = try(each.value.example_file, null) | |||
| instructions_template = try(each.value.instructions_template, null) | |||
There was a problem hiding this comment.
Commented here, but applies to other files: indent?
There was a problem hiding this comment.
Nice, we could move rest of connector instructions with templates like this so we ensure all docs are updated (and no need to keep tf and md versions)
Features
gemini-usageconnector, which includes documentation for setup and usageChange implications