You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm following the guide on how to setup the environment for CI/CD in this repo, and one of the steps we need to run a CURL command that sends a POST request to the AML workspace to configure the runtime for the prompt flow to run. Here is the code example shared in the readme:
When I run this I get an HTTP 405 not allowed response:
405 Not Allowed
I've tried changing the SP permissions to contributor and even owner of the resource, with no luck. I also added the User assigned identity as contributor, but I don't think it is involved in this process at all. I have also tried doing it both locally via cli and also inside the Azure CLI itself, same error on both.
The URL used for the post request looks something like this:
The problem seems to be the way the Compute and Runtimes are now created in AML. You can no longer create a runtime prior to attaching the compute, even the UI won't allow you to do that. So those HTTP calls are no longer valid, there is no reference to any .../api/$region/flow...
I'll try to ignore that step and continue without it, but I suggest updating the guide to reflect these changes.
Hey everyone.
I'm following the guide on how to setup the environment for CI/CD in this repo, and one of the steps we need to run a CURL command that sends a POST request to the AML workspace to configure the runtime for the prompt flow to run. Here is the code example shared in the readme:
When I run this I get an HTTP 405 not allowed response:
405 Not Allowed
I've tried changing the SP permissions to contributor and even owner of the resource, with no luck. I also added the User assigned identity as contributor, but I don't think it is involved in this process at all. I have also tried doing it both locally via cli and also inside the Azure CLI itself, same error on both.
The URL used for the post request looks something like this:
I'm not sure what I could be doing wrong. Is anyone aware of changes to the way to call this API?
The text was updated successfully, but these errors were encountered: