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

[BUG] Extractor failing with subscription id incorrectly formatted #460

Closed
AlnoorAlidina-OMA opened this issue Jan 15, 2024 · 6 comments
Closed
Labels
question Further information is requested

Comments

@AlnoorAlidina-OMA
Copy link

Release version

v5.0.1

Describe the bug

When running the pipeline the extractor is failing with the error:
System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/PaaS/providers/Microsoft.ApiManagement/service/APIM-D/namedValues?api-version=2022-04-01-preview failed with status code 400. Content is '{"error":{"code":"InvalidSubscriptionId","message":"The provided subscription identifier '***' is malformed or invalid."}}'.

However, I checked the variable it has the correct subscription id in the format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Also in the step Set extraction variables the debug print shows the correct subscription id:

image

Not sure what am I missing?

Expected behavior

The extractor should work fine.

Actual behavior

Getting the error described above

Reproduction Steps

Run the extractor pipeline with an account with multiple subscriptions.

Copy link

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

@waelkdouh
Copy link
Contributor

We haven't seen this error before. Is it possible that the subscription is inactive or something odd like that?

@waelkdouh waelkdouh added the question Further information is requested label Jan 16, 2024
@AlnoorAlidina-OMA
Copy link
Author

AlnoorAlidina-OMA commented Jan 16, 2024 via email

@waelkdouh
Copy link
Contributor

I can't see the script you are referring to.

@AlnoorAlidina-OMA
Copy link
Author

AlnoorAlidina-OMA commented Jan 16, 2024 via email

@waelkdouh
Copy link
Contributor

If your issue is resolved please remember to close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants