A subcommand to render manifests and include dependencies

[turkenh]

What problem are you facing?

We have the following two problems which could be resolved together with an intermediate render step:

• When a managed resource depends on other resources, we put them as YAMLs next to the resource we want to test duplicating manifests. For example, in the provider-aws, APIKey depends on GraphQLAPI, and we put it into examples/appsync/apikey.yaml whereas we have examples/appsync/graphqlapi.yaml with the same manifest.
• We have examples published to Upbound Marketplace with uninjected data source values (e.g. ${data.aws_region} , ${data.aws_account_id}) confusing users.

How could Upbound help solve your problem?

Implement a subcommand, e.g., uptest render, which takes care of including manifest YAML (e.g. with an #include statement) from other files and injecting data source values.

• To solve the first problem, we can execute this before running uptest e2e to get complete/ready-to-test example YAMLs.
• To solve the second problem, we can run this with some dummy datasource values (e.g. aws_account_id=1234567890) before publishing examples to the marketplace.