Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Outbound public IP support for AlloyDB instances #2784

Merged

Commits on Oct 3, 2024

  1. Configuration menu
    Copy the full SHA
    7dc30fc View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ba2fd79 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    ec2bdf8 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    28b0cae View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    bc7c728 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    890b697 View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    900ac23 View commit details
    Browse the repository at this point in the history
  8. mockgcp: update AlloyDB golden HTTP logs

    When I had updated the generated AlloyDB protos to include the outbound public IP fields, it also included a new field  on the cluster level. So we need to update various cluster HTTP golden logs. These aren't really related to outbound public IP but are needed for the tests to pass.
    nancynh committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    3d71a42 View commit details
    Browse the repository at this point in the history