Use absolute path for discovery doc#457
Conversation
|
PTAL |
| discovery_doc="/path/to/compute.v1.json", | ||
| toolkit_path='/path/to/toolkit' | ||
| toolkit_path='/path/to/toolkit', | ||
| root_dir='root_dir' |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
b159cc3 to
2d9a8e6
Compare
2d9a8e6 to
dee435f
Compare
| def execute(self, language, toolkit_path, discovery_doc, | ||
| gapic_yaml, package_metadata_yaml, | ||
| gapic_code_dir, api_name, api_version, organization_name): | ||
| gapic_code_dir, api_name, api_version, organization_name, root_dir): |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
I might be missing something - it's unclear for me how the root dir will be used. Why it only applies to one parameter (discovery doc)? |
|
@alexander-fenster However, in discovery-artifact-manager, the relevant discovery document is not in the same directory path as the artman config. PTAL |
garrettjonesgoogle
left a comment
There was a problem hiding this comment.
Ok, let's go with this. LGTM
This allows the artman command line call to run from any directory, e.g. google-cloud-java, not just from inside the discovery_artifact_manager directory.