Skip to content

AIO App Init: Parameterization of input #763

Description

@cmrockwell

Provide parameterization of the input for aio app init to unlock AI code assistant tools to be more effective. All template input data currently needs to be collected interactively. This makes aio app init awkward to call from MCP code generators. For example, in the Assets View UIX MCP (Model Context Protocol) use-case, the following input is collected via interactive CLI

  • Organization
  • Project
  • Extension name
  • Extension description
  • Starting version
  • Server side action
  • Modal
  • Icon
  • Template

As far as I am aware only --template=${template} can be provided via argument. Other data is gathered interactively even if the user had already entered this information into the initial code assistant prompt.

Please add a feature such that arbitrary data can be provided to templates either by providing an args for key/value pairs, or a config parameter which could accept a file path to a yaml file

  • --args='key1=value1,key2=value2'
  • --config=./config.yaml options

The release timeline for the Assets View UIX MCP is Nov. 1, 2025

https://developer.adobe.com/uix/docs/services/aem-assets-view/code-generation/
https://github.com/adobe/aio-cli-plugin-app?tab=readme-ov-file#aio-app-init-path

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions