"Architecture as Code" (AasC) aims to devise and manage software architecture via a machine readable and version-controlled codebase, fostering a robust understanding, efficient development, and seamless maintenance of complex software architectures
As we introduce domains, data models, and other externally linked concerns - we introduce a challenge that the complete information about a given deployment/architecture is located in many different locations and schemas.
We want to bundle this information together to capture the state at the point of various lifecycle events e.g. when deployed.
The bundle command will pull all remote assets into a single bundle, with a manifest file that maps the URIs/URLs to a local JSON file. Examples of what would be bundled include:
Feature Request
Description of Problem:
As we introduce domains, data models, and other externally linked concerns - we introduce a challenge that the complete information about a given deployment/architecture is located in many different locations and schemas.
We want to bundle this information together to capture the state at the point of various lifecycle events e.g. when deployed.
The bundle command will pull all remote assets into a single bundle, with a manifest file that maps the URIs/URLs to a local JSON file. Examples of what would be bundled include:
detailed-architecture