Open lucaippi opened 3 months ago
You can try the suggestion from https://github.com/Netflix-Skunkworks/policyuniverse/issues/184#issuecomment-2118036606
@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
Hey @smoy, sorry for missing this before. This project is still maintained, though it has not been something we've been able to prioritize. I'm definitely open to changing how the updater works. We come through and fix it occasionally, but it's super brittle and ends up breaking again shortly after.
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?