aimtool icon indicating copy to clipboard operation
aimtool copied to clipboard

Handling custom components

Open EldertGrootenboer opened this issue 3 years ago • 1 comments

Description

How should we handle custom components, f.e. in pipelines and orchestrations. When we now run this, the script fails and stops, not creating the components. Is there any way to work around this?

Custom components issue

Environment and tool versions

  • AIM Tool Version (aim --version):
  • Windows Version (systeminfo):
  • Shell: (PowerShell | Bash)
  • Shell Version ($PSVersionTable | bash --version):

Repro steps

Use the tool with an MSI with custom components

Expected result

Tool successfully processes the MSI with no errors.

Current result

The tool stops and outputs an error.

EldertGrootenboer avatar May 19 '21 07:05 EldertGrootenboer

Can you give examples of custom components that are failing? Ideally, the tool should fail gracefully without causing an error. In terms of support for custom components, it's a tricky thing - the tool doesn't know what they do. In some cases, AIS already has an equivalent for things that people write custom components for.

There was a conversation about looking at custom components and the assemblies they use and trying to work out if they could be supported, e.g. hosting custom assemblies in a Function.

What would you like to see, i.e. what would be most useful?

probertdaniel avatar Jun 29 '21 06:06 probertdaniel