Skip to content
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
This repository was archived by the owner on Mar 19, 2026. It is now read-only.

Update IAMPolicy mixin to use <$service>.yaml file instead of explicit generator flag #612

Closed

Description

@alicejli

As part of adding support generally for client library mixin method generations (draft AIP is at aip-dev/google.aip.dev#694), this update is to move the generator from reading the google.iam.v1.IAMPolicy mixin as an explicit generator flag to reading it from the <$service>.yaml file.

This change should not impact functionality in any way, as each API that had the explicit mixin flag should also have it listed in their <$service>.yaml file.

Ping me for the internal doc(s) if desired.

Activity

  1. added
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    priority: p3Desirable enhancement or fix. May not be included in next release.
    on Jun 29, 2021
  2. alicejli commented on Jul 22, 2021

    @alicejli
    ContributorAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p3Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions