You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When filtering for a given service at least two main linked services are causing a headache and a lot of manual cleanup on the generated code ( IAM and Networking ) .
However including them in the rendered IaC code isn't a good default either, as they could be input parameters ( CFN ) or just being located based on a given property ( TF data provider )
My suggestion is when filtered code render is requested, then the render should took three stages.
Scan the account for the requested scope but follow the links references ( IAM roles, Network elements )
Render in a graph the scan result and let the user pick which linked resource to include, exclude, or just refer to based on some property of the resource
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When filtering for a given service at least two main linked services are causing a headache and a lot of manual cleanup on the generated code ( IAM and Networking ) .
However including them in the rendered IaC code isn't a good default either, as they could be input parameters ( CFN ) or just being located based on a given property ( TF data provider )
My suggestion is when filtered code render is requested, then the render should took three stages.
Beta Was this translation helpful? Give feedback.
All reactions