feat(tools/looker): add ability to set destination folder with make_look and make_dashboard.

[drstrangelooker]

Description

When running with a service account, the user has no personal folder id. This allows a destination
folder to be specified as part of the call to make_dashboard and make_look. If a folder is not specified
the user's personal folder will be used.

PR Checklist

Thank you for opening a Pull Request! Before submitting your PR, there are a
few things you can do to make sure it goes smoothly:

• Make sure you reviewed
  CONTRIBUTING.md
• Make sure to open an issue as a
  bug/issue
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)
• Make sure to add ! if this involve a breaking change

🛠️ Fixes #2225

[gemini-code-assist]

Summary of Changes

Hello @drstrangelooker, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Looker tools by adding the capability to specify a target folder when creating new Looks and Dashboards. This is particularly beneficial for automated processes or service accounts that may not have a default personal folder, ensuring that Looker assets can be organized and created in designated locations. The change provides greater flexibility and robustness to the Looker integration.

Highlights

• New Folder Parameter: Introduced an optional folder parameter to both make_look and make_dashboard functions, allowing users to specify a destination folder for created Looker assets.
• Service Account Compatibility: This change addresses the limitation where service accounts lack a personal folder ID, enabling them to create Looker assets by explicitly providing a folder ID.
• Default Folder Logic: If no folder is specified, the system will attempt to use the user's personal folder. If a personal folder is unavailable (e.g., for service accounts) and no folder ID is provided, an error will now be returned, requiring a folder to be specified.
• Documentation and Tests: Updated documentation for looker-make-dashboard and looker-make-look to reflect the new parameter, and added integration tests to validate its functionality.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the ability to specify a destination folder when creating Looks and Dashboards in Looker. This is a useful feature, especially for service accounts that may not have a personal folder. The implementation looks good, with updates to the tool definitions, invocation logic, and documentation. I've made a couple of suggestions to simplify the folder resolution logic for better readability.

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2245/

[Yuan325]

Thank you!

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2245/

[github-actions]

🧨 Preview deployments removed.