Skip to content

Add legacy_publish_attribute flag to indicate whether to check for the legacy publish attribute.#14

Open
cloud-healthcare-github wants to merge 1 commit into
masterfrom
cl_303745770
Open

Add legacy_publish_attribute flag to indicate whether to check for the legacy publish attribute.#14
cloud-healthcare-github wants to merge 1 commit into
masterfrom
cl_303745770

Conversation

@cloud-healthcare-github
Copy link
Copy Markdown
Collaborator

Add legacy_publish_attribute flag to indicate whether to check for the legacy publish attribute.

By default the MLLP adapter will skip checking for the attribute and thus messages created from both the messages.ingest method and the messages.create method will be forwarded by the MLLP adapter.

@googlebot
Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@cloud-healthcare-github cloud-healthcare-github force-pushed the cl_303745770 branch 8 times, most recently from c713d7e to 5674435 Compare March 31, 2020 14:12
PiperOrigin-RevId: 303745770
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.

2 participants