-
Notifications
You must be signed in to change notification settings - Fork 61
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
Updater Action does not work since a few months #186
Comments
You can try the suggestion from #184 (comment) |
@smoy the issue was not really resolved in the thread you referenced right? @patricksanders mentioned that the updated logic could be updated to something more stable but it was not so far. I guess there are many options that could be used as datasource for this
curl --header 'Connection: keep-alive' \
--header 'Pragma: no-cache' \
--header 'Cache-Control: no-cache' \
--header 'Accept: */*' \
--header 'Referer: https://awspolicygen.s3.amazonaws.com/policygen.html' \
--header 'Accept-Language: en-US,en;q=0.9' \
--silent \
--compressed \
'https://awspolicygen.s3.amazonaws.com/js/policies.js' |
cut -d= -f2 |
jq -r '.serviceMap[] | .StringPrefix as $prefix | .Actions[] | "\($prefix):\(.)"' |
sort |
uniq
So the issue is still open and what could be challenged is weather the current updater logic should be fixed or replaced |
@lucaippi It's not resolved. Since policyuniverse is mostly in maintenance mode, I actually just have my own implementation that converts iam-dataset to the existing policyuniverse format and replace data.json
|
I noticed that the updater action does not work since around 9 months
It seems like PhantomJS has issues executing awsconsole.js - tried some things locally, but given I am no expert with node/js I could not find a solution right away. Any idea on how to make this work again?
The text was updated successfully, but these errors were encountered: