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

Terraform resource for Azure AML workspace datastore- "azurerm_machine_learning_datastore_datalake_gen2" endpoint issue for Storage container ID deploying to US gov #22467

Closed
1 task done
rej007 opened this issue Jul 11, 2023 · 4 comments · Fixed by #24798

Comments

@rej007
Copy link

rej007 commented Jul 11, 2023

Is there an existing issue for this?

  • I have searched the existing issues

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 and review the contribution guide to help.

Description

should be an option provide endpoint if default endpoint is not "core.windows.net" for storage account

New or Affected Resource(s)/Data Source(s)

azurerm_machine_learning_datastore_datalake_gen2

Potential Terraform Configuration

I believe there should be an option to provide a different endpoint because the default endpoint is "core.windows.net", which might not be the case for all storage accounts

References

No response

@rej007
Copy link
Author

rej007 commented Jul 11, 2023

Resource Group Name: "test-rg”
│ Workspace Name: "exampleworkspace"
│ Data Store Name: "exampledatastore"): datastore.DatastoreClient#CreateOrUpdate: Failure responding to request: StatusCode=400 --
│ Original Error: autorest/azure: Service returned an error. Status=400 Code="Invalid" Message="Invalid endpoint. Provided:
│ [core.windows.net], Expected: [core.usgovcloudapi.net]" Details=[]

@rej007 rej007 changed the title Terraform resource for Azure AML workspace datastore- "azurerm_machine_learning_datastore_datalake_gen2" endpoint issue for Storage container ID Terraform resource for Azure AML workspace datastore- "azurerm_machine_learning_datastore_datalake_gen2" endpoint issue for Storage container ID deploying to US gov Jul 11, 2023
@stonenw-va
Copy link

Yes Same Error as rej007
creating Data Store (Subscription:
│ Resource Group Name: "RG"
│ Workspace Name: "aml"
│ Data Store Name: "datastore"): unexpected status 400 with error: Invalid: Invalid
│ endpoint. Provided: [core.windows.net], Expected: [core.usgovcloudapi.net]

@rej007
Copy link
Author

rej007 commented Feb 27, 2024

@manicminer

@manicminer manicminer self-assigned this Feb 27, 2024
@manicminer manicminer added the bug label Feb 27, 2024
manicminer added a commit that referenced this issue Mar 1, 2024
…hine_learning_datastore_blobstorage`, `azurerm_machine_learning_datastore_datalake_gen2` and `azurerm_machine_learning_datastore_fileshare` resources. closes: #22467
manicminer added a commit that referenced this issue Mar 1, 2024
…hine_learning_datastore_blobstorage`, `azurerm_machine_learning_datastore_datalake_gen2` and `azurerm_machine_learning_datastore_fileshare` resources. closes: #22467
reastyn pushed a commit to reastyn/terraform-provider-azurerm that referenced this issue Mar 14, 2024
…hine_learning_datastore_blobstorage`, `azurerm_machine_learning_datastore_datalake_gen2` and `azurerm_machine_learning_datastore_fileshare` resources. closes: hashicorp#22467
Copy link

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 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants