[go: nahoru, domu]

Skip to content
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

WIP: Update logging gapic yaml #208

Merged

Conversation

michaelbausor
Copy link
Contributor

Updates logging to use resource names

Added folder and billingAccounts
Moved new formats to top-level collection config, so that additional
format and parse methods are not generated
collection_oneofs:
- oneof_name: parent_oneof
collection_names:
- parent
- organization
- folder
- billing
- oneof_name: sink_oneof
collection_names:
- sink

This comment was marked as spam.

- oneof_name: sink_oneof
collection_names:
- sink
- organization_sink
- folder_sink
- billing_sink
- oneof_name: log_oneof
collection_names:
- log

This comment was marked as spam.

@@ -19,6 +19,55 @@ language_settings:
license_header:
copyright_file: copyright-google.txt
license_file: license-header-apache-2.0.txt
collections:
- name_pattern: projects/{project}
entity_name: parent

This comment was marked as spam.

Rename parent collection to project
Rename log to project_log
Rename sink to project_sink
Copy link
Contributor Author
@michaelbausor michaelbausor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated with these changes. Definitely agree about parent->project.

I can see the argument both ways for log vs project_log and sink vs. project_sink. They are the most common, so there is an advantage to keeping the names simple, even if that is less consistent with the others.

@garrettjonesgoogle
Copy link
Member

LGTM

@michaelbausor michaelbausor merged commit 3588d87 into googleapis:master Dec 7, 2016
@michaelbausor michaelbausor deleted the logging-resource-names branch December 7, 2016 01:29
jmuk added a commit to jmuk/gcloud-node that referenced this pull request Dec 8, 2016
This regeneration is for googleapis/googleapis#208.

Basically, it changes the name of 'parentPath' to 'projectPath',
and we believe the new name is more understandable.

This regeneration happens to include a minor change on the codegen
to support LRO -- however this does not require any updates on
dependencies. Simple style changes.
stephenplusplus pushed a commit to googleapis/google-cloud-node that referenced this pull request Dec 8, 2016
This regeneration is for googleapis/googleapis#208.

Basically, it changes the name of 'parentPath' to 'projectPath',
and we believe the new name is more understandable.

This regeneration happens to include a minor change on the codegen
to support LRO -- however this does not require any updates on
dependencies. Simple style changes.
@bjwatson
Copy link
Contributor
bjwatson commented Dec 9, 2016

Forgot to remove "WIP" from the commit message. ;)

@michaelbausor
Copy link
Contributor Author

Oops... do you think this is worth amending and force-pushing to update?

@bjwatson
Copy link
Contributor
bjwatson commented Dec 9, 2016

No, let's not force update anything on master. Just pointing out in case anyone is wondering why a WIP was merged ('cause it's not really a WIP anymore).

@michaelbausor
Copy link
Contributor Author

OK no worries!

stephenplusplus pushed a commit to googleapis/nodejs-logging that referenced this pull request Sep 22, 2017
This regeneration is for googleapis/googleapis#208.

Basically, it changes the name of 'parentPath' to 'projectPath',
and we believe the new name is more understandable.

This regeneration happens to include a minor change on the codegen
to support LRO -- however this does not require any updates on
dependencies. Simple style changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants