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

Support healthcare dicom bq stream configure #8958

Closed
chaopeng opened this issue Apr 20, 2021 · 1 comment · Fixed by GoogleCloudPlatform/magic-modules#4717, #8986 or hashicorp/terraform-provider-google-beta#3190

Comments

@chaopeng
Copy link

chaopeng commented Apr 20, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Feature is in beta now.

https://cloud.google.com/healthcare/docs/how-tos/dicom-bigquery-streaming#healthcare-streaming-dicom-metadata-cli-curl

New or Affected Resource(s)

  • google_healthcare_hl7_v2_store

Potential Terraform Configuration

      - !ruby/object:Api::Type::Array
        name: streamConfigs
        required: false
        min_version: beta
        update_url: '{{dataset}}/dicomStores/{{name}}'
        description: |
          To enable streaming to BigQuery, configure the streamConfigs object in your DICOM store.
          streamConfigs is an array, so you can specify multiple BigQuery destinations. You can stream metadata from a single DICOM store to up to five BigQuery tables in a BigQuery dataset.
        item_type: !ruby/object:Api::Type::NestedObject
          properties:
            - !ruby/object:Api::Type::NestedObject
              name: bigqueryDestination
              required: true
              description: |
                BigQueryDestination to include a fully qualified BigQuery table URI where DICOM instance metadata will be streamed.
              properties:
                - !ruby/object:Api::Type::String
                  name: tableUri
                  required: true
                  description: |
                    a fully qualified BigQuery table URI where DICOM instance metadata will be streamed.

References

@ghost
Copy link

ghost commented May 24, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators May 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.