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

google_datafusion_instance add support for accelerators #9070

Comments

@Guimove
Copy link

Guimove commented May 4, 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

During the creation of a Data Fusion Instance, we can enable some "accelerators" (actually only replication). This is not supported by the provider for the moment.

New or Affected Resource(s)

  • google_datafusion_instance

Potential Terraform Configuration

resource "google_data_fusion_instance" "instance" {
  provider                      = google-beta
  name                          = "datafusion"
  description                   = "datafusion instance"
  region                        = "europe-west-2"
  type                          = "developer"
  enable_stackdriver_logging    = false
  enable_stackdriver_monitoring = false
  private_instance              = false
  version                       = "6.4.0"
  accelerators {
    "replication",
    "list_of_accelerators"
  }
}

References

image

@rileykarson rileykarson added this to the Goals milestone May 10, 2021
@Guimove
Copy link
Author

Guimove commented Jul 21, 2021

Hello,

Do you have any news about that feature ?

Actually, I’m using a custom null_resource to run after the instance creation :

curl -H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "Content-Type: application/json" \
${CDAP_ENDPOINT}  -X PATCH -d '{ "accelerators":[{"accelerator_type":"CDC", "state":"ENABLED"}]}'

But this is not really flexible.

This is major for us

@shuyama1
Copy link
Collaborator

Waiting for b/199551875 to be fixed.

@dmccaffery
Copy link

@shuyama1 - I am happy to take this on if b/199551875 has been resolved. I cannot find any reference to an issue with that id (I assume its an internal bug). If work on this is ready to go, I am happy to submit a PR -- just let me know.

@a1031
Copy link

a1031 commented Jun 17, 2022

@dmccaffery Indeed, it seems like b/199551875 is an internal/non-public bug on the Google Issue Tracker for Cloud Data Fusion - if I visit https://issuetracker.google.com/issues/199551875 I get Access denied for: <email>, and if I visit the same link but with a higher number that wouldn't exist I get Issue <number> does not exist (example: https://issuetracker.google.com/issues/999551875).

@melinath
Copy link
Collaborator

melinath commented Sep 9, 2022

b/245981973

@github-actions
Copy link

github-actions bot commented Apr 9, 2023

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.