-
Notifications
You must be signed in to change notification settings - Fork 53
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
chore: remove template_excludes
in the generation config
#2801
Conversation
@@ -1,19 +1,5 @@ | |||
gapic_generator_version: 2.40.2-SNAPSHOT | |||
googleapis_commitish: 3d50414a7ff3f0b8ffe8ad7858257396e4f18131 | |||
template_excludes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the behavior now this is removed? From the logic here, it should be fine for existing libraries. If we want to create new libraries with empty template_excludes
, are we going to create an owlbot.py with empty template_excludes
section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to create new libraries with empty template_excludes, are we going to create an owlbot.py with empty template_excludes section?
Yes, the exclusions in owlbot.py is empty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did we populate it before without hermetic build? Maybe we can populate a default list like this?
".github/*",
".kokoro/*",
"samples/*",
"CODE_OF_CONDUCT.md",
"CONTRIBUTING.md",
"LICENSE",
"SECURITY.md",
"java.header",
"license-checks.xml",
"renovate.json",
".gitignore"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's hard coded in the new-client.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was hardcode in new-client.py
, but since it does not exist anymore, is it still hardcoded somewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the only place that may have template exclusions is generation config.
This parameter is used to generate owlbot.py
if it doesn't exist. Since we don't have this situation, we can remove this parameter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we hardcode it somewhere in our code? So that we don't have to specify it anymore in google-cloud-java?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed template_exclusions
from the config.
Quality Gate passed for 'gapic-generator-java-root'Issues Measures |
template_excludes
a non-required parametertemplate_excludes
in the generation config
Quality Gate passed for 'java_showcase_integration_tests'Issues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we still confirm the template excludes behave correctly using the owlbot.py golden test, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the unit test is not changed.
In this PR:
template_excludes
in the generation configREADME.md
Follow up of #2792.