Remove Azimuth team

[priteau]

This is not needed anymore: Azimuth repositories have moved to https://github.com/azimuth-cloud.

[gemini-code-assist]

Summary of Changes

Hello @priteau, 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 streamlines the GitHub team configurations by removing the 'Azimuth' team. This change reflects the migration of Azimuth-related repositories to a new, dedicated GitHub organization, thereby cleaning up outdated infrastructure definitions.

Highlights

• Team Removal: The 'Azimuth' team configuration has been removed from the GitHub Terraform variables.
• Reason for Removal: This team is no longer needed as Azimuth repositories have migrated to a new GitHub organization.

Changelog

• terraform/github/terraform.tfvars.json
  • Removed the 'Azimuth' team definition.

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 removes the 'Azimuth' team definition from the terraform.tfvars.json configuration file. The change is consistent with the pull request description, which states that the Azimuth repositories have been moved. I have reviewed the related Terraform configuration files and confirmed that there are no dangling references to the 'Azimuth' team. The change is correct and complete.

[Alex-Welsh]

https://github.com/stackhpc/stackhpc-release-train/blob/main/terraform/github/import_resources.py#L98
This can probably be removed too

[priteau]

https://github.com/stackhpc/stackhpc-release-train/blob/main/terraform/github/import_resources.py#L98 This can probably be removed too

Indeed, but I wasn't sure if it we might need to remove it once the team is deleted. The remaining issue is working around the prevent_destroy Terraform setting. Or maybe we just delete the team manually?