google/iam/v1 and google/iam/v1beta are configured to in generation_config.yaml:
|
- api_shortname: iam-policy |
|
name_pretty: IAM |
|
product_documentation: n/a |
|
api_description: n/a |
|
release_level: stable |
|
distribution_name: com.google.cloud:google-iam-policy |
|
api_id: iam.googleapis.com |
|
client_documentation: https://cloud.google.com/java/docs/reference/proto-google-iam-v1/latest/history |
|
excluded_poms: proto-google-iam-v1-bom,google-iam-policy,proto-google-iam-v1 |
|
excluded_dependencies: google-iam-policy |
|
GAPICs: |
|
- proto_path: google/iam/v1 |
|
- proto_path: google/iam/v1beta |
|
- proto_path: google/iam/v2 |
|
- proto_path: google/iam/v2beta |
|
- proto_path: google/iam/v3 |
|
- proto_path: google/iam/v3beta |
However, they are not copied in .OwlBot-hermetic.yaml. So even though generated, it is not copied to final location.
Is this intentional?
For now, I propose to remove these paths from generation_config.yaml for consistency.
Then, If we desire to add these to generated code, we can:
- update .OwlBot-hermetic.yaml to copy v1 and v1beta now before migration
- update librarian.yaml after migration to librarian
google/iam/v1andgoogle/iam/v1betaare configured to in generation_config.yaml:google-cloud-java/generation_config.yaml
Lines 1327 to 1343 in 2312aae
However, they are not copied in .OwlBot-hermetic.yaml. So even though generated, it is not copied to final location.
Is this intentional?
For now, I propose to remove these paths from generation_config.yaml for consistency.
Then, If we desire to add these to generated code, we can: