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

Unique ID GitHub Action - parsing failure fix and wording update #492

Merged
merged 7 commits into from
Feb 6, 2025

Conversation

Joshua-Donovan
Copy link
Collaborator

#491
Root Cause:
I was able to find the source file we are getting from https://www.azadvertizer.net is now large enough that it is being compressed to binary and therefore was failing to be parsed by the JSON parser in bash.

Solution:
Added the --compressed flag to the curl request to handle the compression of the file.

Extra Testing:
Validated the --compressed flag in curl would not throw an error when downloading an uncompressed file so this should not be a breaking change if we start receiving an uncompressed response from azadvertizer.net again.

#477
While in the code I also added the wording improvements to this script to remove the direct references to built-in definitions and to keep the responses more generic / inclusive of the fact that we can also match community policies with this data source.

@aschabus aschabus merged commit 4057d18 into Azure:main Feb 6, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants