Closed aunraza closed 8 months ago
hey @aunraza thanks for reaching out.
There are actually a couple of issues not handled correctly.
Those actions don't exist in the internal DB, which is updated at the beginning of each month:
Even after removing them, there 2 special cases, which are not handled correctly and result in the mentioned error. For some reason the ARNs of Portfolio
and Product
under Service Catalog use catalog
as service name and not servicecatalog
. Additionally the ARN of recoveryPoint
under Backup has the placeholder ${Vendor}
.
When I try to write-policy (
policy_sentry write-policy --input-file actions.yml -m
)using the attached file (renamed extension to .txt instead of .yml) actions.txt, I get the following error:I am unable to determine which actions are causing this problem. It works in certain cases so it likely seems to be failing on some action - I wasn't able to pinpoint it as the debugs don't show which action.