Closed joetancy closed 3 years ago
this issue isnt coming from this plugin, but instead from clouddriver https://github.com/spinnaker/clouddriver/blob/master/clouddriver-lambda/src/main/java/com/netflix/spinnaker/clouddriver/lambda/provider/agent/LambdaCachingAgent.java
This happens when the aws user has any deny policy in lambda:ListVersionsByFunction on any function that is not the application in Spinnaker.
Apparently, this also affects the UI component, where when the aws account has a deny policy like above, even though there's a cluster group created (to get around the UI big mentioned here https://github.com/spinnaker/spinnaker/issues/6271), this same exception still appears.
I have no fix for this and is looking for advice. will also attempt to fix if someone could point me in the right direction. thank you!