How can a DevOps Engineer expose values from a child module that defines AWS VPC resources to the CLI?

To expose values from a child module to the Command Line Interface (CLI), it's essential to define outputs in both the parent and child module. Here's why this approach is necessary:

When a child module is defined, it typically contains resources and logic that are encapsulated within it. However, to access specific values or attributes of the resources defined in the child module from the parent module (or directly from the CLI), output variables must be created in the child module. This allows the child module to expose specific data points, such as VPC IDs, subnet IDs, or other resource attributes that are created within that module.

Once outputs are declared in the child module, the parent module can access these outputs through an output block defined in the parent. This layer of output declaration allows for a modular approach, wherein the parent module can reference values created in the child module without exposing all internal workings of the child module directly.

Typically, if only the child module defined outputs but not the parent, the parent wouldn't naturally have a way to access those outputs directly via the CLI. Therefore, to facilitate communication and make those child module outputs available to the command line or for further processing, outputs must be defined in both locations.

In essence, defining outputs in both