hermetic build script here, only checks in proto-google-* dirs.
There are 3 proto modules that do not match the proto-google-* pattern:
google-cloud-java/java-marketingplatformadminapi/proto-admin-v1alpha
google-cloud-java/java-admanager/proto-ad-manager-v1
google-cloud-java/java-datamanager/proto-data-manager-v1
These modules are skipped by the hermetic build's write_clirr_ignore.sh script due to the hardcoded proto-google-* glob pattern.
For migration sake, changed librarian code to do the same. Separately, wonder if this was a miss in hermetic build script or intentional? @blakeli0 @diegomarquezp
We can remove the condition and generate for these after migration if this was not intentional.
Context: googleapis/librarian#5558
hermetic build script here, only checks in proto-google-* dirs.
There are 3 proto modules that do not match the proto-google-* pattern:
google-cloud-java/java-marketingplatformadminapi/proto-admin-v1alpha
google-cloud-java/java-admanager/proto-ad-manager-v1
google-cloud-java/java-datamanager/proto-data-manager-v1
These modules are skipped by the hermetic build's write_clirr_ignore.sh script due to the hardcoded proto-google-* glob pattern.
For migration sake, changed librarian code to do the same. Separately, wonder if this was a miss in hermetic build script or intentional? @blakeli0 @diegomarquezp
We can remove the condition and generate for these after migration if this was not intentional.
Context: googleapis/librarian#5558