sdk discovery

[webern]

Description

There may be cases where it is convenient not to specify which Bottlerocket SDK is preferred. Additionally there may be overlapping cases where this cannot be inferred from dependence on the bottlerocket-core-kit.

Furthermore, there may be cases where Twoliter needs to use the SDK before it knows what SDK the relevant kits were built with. For example, when it is doing dependency resolution of the specified kit dependencies, it will not yet have

We need to figure out:

• How the user should specify the desired SDK when the required one cannot be determined
• How twoliter should do dependency resolution, which needs to occur before the correct SDK is known
• How twoliter should know which target arch SDK to pull if it is doing something where target arch doesn't matter

In general the goal is to avoid pulling the wrong SDK just so that we can find out what the right SDK is.

Definition of Done

When

• [ ] the design document is refined to explain how we can avoid pulling the wrong SDK before we know what SDK we need
• [ ] the described mechanism has been implemented

Depends on:

• [x] https://github.com/bottlerocket-os/twoliter/issues/10

id: texec_default_sdk
epic: twoliter_exec

Related to https://github.com/bottlerocket-os/bottlerocket/issues/2669