Remove Backstage references

[brettcurtis]

Summary by CodeRabbit

• New Features

  • The "Backstage" service has been completely removed from the system, including its configurations and IAM policies across Sandbox and Production environments.

• Impact on Users

  • Users associated with the "Backstage" service will no longer have access or permissions tied to it due to the removal of identity groups and IAM roles.

[infracost]

💰 Infracost report

Monthly estimate generated

Estimate details (includes details of unsupported resources)

──────────────────────────────────
1 project has no cost estimate change.
Run the following command to see its breakdown: infracost breakdown --path=/path/to/code

──────────────────────────────────
144 cloud resources were detected:
∙ 0 were estimated
∙ 43 were free
∙ 101 are not supported yet, see https://infracost.io/requested-resources:
  ∙ 43 x google_cloud_identity_group_membership
  ∙ 34 x google_folder
  ∙ 15 x google_cloud_identity_group
  ∙ 9 x google_billing_budget

_{This comment will be updated when code changes.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent changes involve the complete removal of the "Backstage" service from the system, affecting IAM policies, service configurations, and identity groups. This elimination includes the deletion of role bindings, the service's display name, and all associated identity management elements. The changes indicate a significant shift in how services are managed within the environment, with "Backstage" no longer recognized in any capacity.

Changes

Files	Change Summary
tfvars/production.tfvars	Removal of IAM policy configurations for service IDs 717171519290 and 38257772554; removal of service configuration for service-8; deletion of identity groups backstage and backstage-sb.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.