sparse-intern-71089
07/20/2020, 10:25 AMcolossal-beach-47527
07/21/2020, 5:55 PMstocky-lion-56153
07/21/2020, 6:09 PMroute53:GetChange
in order to work with route53 DNS records is not immediately obvious, Is there an area of the Pulumi source code I’d benefit from learning more about?stocky-lion-56153
07/21/2020, 6:10 PMpulumi up
and then pulumi refresh
and pulumi destroy
with admin privs and then lock down the user according to what was logged. Unfortunately nothing like that exists AFAIK.colossal-beach-47527
07/21/2020, 6:41 PMFor instance, the need to grantA first approximation would be thein order to work with route53 DNS records is not immediately obviousroute53:GetChange
route53:Get*
and route53:List*
. But every service has its own quirks, e.g. there used to be an s3:HeadObject
action.
There isn’t any place in the source code that would be especially helpful other than the underlying resource provider’s source code. (But even that is using CRUD APIs to create or update resources, and there isn’t always a clear mapping from API method and the IAM Action needed to call/use that API.
… as for some sort of audit log of what actions were used during a pulumi up
and pulumi refresh
, etc. I don’t know of anything either. I know CloudTrail would give you a lot of the API calls used, but I don’t know off the top of my head if it also lists the specific IAM actions used, and Resource ARNs that were operated on.
All of this to say is that it’s a known problem, but I don’t know of any good solutions to it. But I wouldn’t be surprised if our beloved cloud provider overlords would release some offering to help us in this regard. Since this problem isn’t unique to Pulumi or AWS. And certainly be a “big deal” if GCP or Azure were to provide this capability… 🤞🏽stocky-lion-56153
07/21/2020, 6:45 PMstocky-lion-56153
07/21/2020, 6:48 PM