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

feat(AIP-133): add request-id-field for non-df API #1155

Merged
merged 2 commits into from
May 22, 2023
Merged

feat(AIP-133): add request-id-field for non-df API #1155

merged 2 commits into from
May 22, 2023

Conversation

toumorokoshi
Copy link
Contributor

@toumorokoshi toumorokoshi commented May 19, 2023

Corresponds to the change to aip-dev/google.aip.dev#1019.

resource_id is now required regardless of declarative_friendly.

fixes #1107

Corresponds to the change to aip-dev/google.aip.dev#1019.

resource_id is now required regardless of declarative_friendly.
@toumorokoshi toumorokoshi requested a review from a team as a code owner May 19, 2023 05:09
@toumorokoshi toumorokoshi added this to the gcp-strict-aips milestone May 19, 2023
rules/aip0133/request_id_field_test.go Outdated Show resolved Hide resolved
- removed redundant test
@toumorokoshi toumorokoshi merged commit 2787792 into googleapis:main May 22, 2023
@SsomsakTH
Copy link

Corresponds to the change to aip-dev/google.aip.dev#1019.

resource_id is now required regardless of declarative_friendly.

fixes #1107

@SsomsakTH
Copy link

Corresponds to the change to aip-dev/google.aip.dev#1019.

resource_id is now required regardless of declarative_friendly.

fixes #1107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

request {resource}_id even if the resource is not declarative-friendly.
3 participants