- From data structure to painless
- From data painless to da structure
- Create API
- Create Front Endx
- Add Testing capabilities
-
Arrays
- Multiple array levels is complex to parse/convert in painless
- For performance measures, ideally we group nested fields in a same loop, for example, we might want
to extract
a[].banda[].c. Instead of having two loops ona, ideally we have one loop onaextractingbandc. This is important from a performance standpoint - read Loops with multilevel access after loop (e.g.
json.responseElements.securityGroupRuleSet.items[].referencedGroupInfo.groupId) - read Loops with multilevel access after loop (e.g.
json.responseElements.securityGroupRuleSet.items[].referencedGroupInfo.groupId) because it needs to have optional markers, it needs to becomereferencedGroupInfo?.groupId - arrays without further values, e.g
json.requestParameters.alarmNames[]
-
Special Cases
- dash containing sources e.g
ec2-instance-connect - lambda that has versioning at the end of the event, it's is not
AddPermissionbutAddPermission20250101 SendCommandlogic of if pointed to all instances (*), add full account as targetAssumeRolehas different target based on type of user type
- dash containing sources e.g
-
Actor per event
- not yet implemented