forked from GoogleCloudPlatform/magic-modules
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow fields to be removed at a specific version (GoogleCloudPlatform…
…#3417) The healthcare API has deprecated a field at beta and removed it from the GA launch of the api. In order to support this without having to duplicate the entire resource this change supports defining a single field multiple times with a different configruation for each version. Specifically it allows a field to exist as deprecated at one version but not at another. This also introduces the removed_message field.
- Loading branch information
Showing
11 changed files
with
92 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -375,9 +375,62 @@ objects: | |
An object containing a list of "key": value pairs. | ||
Example: { "name": "wrench", "mass": "1.3kg", "count": "3" }. | ||
- !ruby/object:Api::Type::Array | ||
name: notificationConfigs | ||
description: |- | ||
A list of notification configs. Each configuration uses a filter to determine whether to publish a | ||
message (both Ingest & Create) on the corresponding notification destination. Only the message name | ||
is sent as part of the notification. Supplied by the client. | ||
item_type: !ruby/object:Api::Type::NestedObject | ||
properties: | ||
- !ruby/object:Api::Type::String | ||
name: pubsubTopic | ||
description: | | ||
The Cloud Pub/Sub topic that notifications of changes are published on. Supplied by the client. | ||
PubsubMessage.Data will contain the resource name. PubsubMessage.MessageId is the ID of this message. | ||
It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message | ||
was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a | ||
project. [email protected] must have publisher permissions on the given | ||
Cloud Pub/Sub topic. Not having adequate permissions will cause the calls that send notifications to fail. | ||
If a notification cannot be published to Cloud Pub/Sub, errors will be logged to Stackdriver | ||
required: true | ||
- !ruby/object:Api::Type::String | ||
name: filter | ||
description: | | ||
Restricts notifications sent for messages matching a filter. If this is empty, all messages | ||
are matched. Syntax: https://cloud.google.com/appengine/docs/standard/python/search/query_strings | ||
Fields/functions available for filtering are: | ||
* messageType, from the MSH-9.1 field. For example, NOT messageType = "ADT". | ||
* send_date or sendDate, the YYYY-MM-DD date the message was sent in the dataset's timeZone, from the MSH-7 segment. For example, send_date < "2017-01-02". | ||
* sendTime, the timestamp when the message was sent, using the RFC3339 time format for comparisons, from the MSH-7 segment. For example, sendTime < "2017-01-02T00:00:00-05:00". | ||
* sendFacility, the care center that the message came from, from the MSH-4 segment. For example, sendFacility = "ABC". | ||
* PatientId(value, type), which matches if the message lists a patient having an ID of the given value and type in the PID-2, PID-3, or PID-4 segments. For example, PatientId("123456", "MRN"). | ||
* labels.x, a string value of the label with key x as set using the Message.labels map. For example, labels."priority"="high". The operator :* can be used to assert the existence of a label. For example, labels."priority":*. | ||
- !ruby/object:Api::Type::NestedObject | ||
name: notificationConfig | ||
removed_message: This field has been replaced by notificationConfigs | ||
exact_version: ga | ||
required: false | ||
update_url: '{{dataset}}/hl7V2Stores/{{name}}' | ||
properties: | ||
- !ruby/object:Api::Type::String | ||
name: pubsubTopic | ||
description: | | ||
The Cloud Pub/Sub topic that notifications of changes are published on. Supplied by the client. | ||
PubsubMessage.Data will contain the resource name. PubsubMessage.MessageId is the ID of this message. | ||
It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message | ||
was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a | ||
project. [email protected] must have publisher permissions on the given | ||
Cloud Pub/Sub topic. Not having adequate permissions will cause the calls that send notifications to fail. | ||
required: true | ||
- !ruby/object:Api::Type::NestedObject | ||
name: notificationConfig | ||
# This field is duplicated because beta and ga have different behaviors. | ||
deprecation_message: This field has been replaced by notificationConfigs | ||
exact_version: beta | ||
required: false | ||
update_url: '{{dataset}}/hl7V2Stores/{{name}}' | ||
properties: | ||
|
@@ -391,7 +444,6 @@ objects: | |
project. [email protected] must have publisher permissions on the given | ||
Cloud Pub/Sub topic. Not having adequate permissions will cause the calls that send notifications to fail. | ||
required: true | ||
|
||
- !ruby/object:Api::Type::Time | ||
name: 'creationTime' | ||
description: | | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters