...
- Provide a Model driven framework to help ONAP community and ONAP end-user to develop the required commands
- By using YAML file and without writing any source code
- By implementing plug-ins for specific commands
- Provide direct command mode (useful in scripting based automation) like in CI, docker, etc
- Provide interactive mode, where user login once and operate ONAP and exit
- Provide consistent commands schematics across different ONAP functionalities.
Architecture Alignment:
- Dependencies
- ONAP CLI uses REST API to communicate with ONAP, so it depends on the ONAP API documentation project
- ONAP authendication service REST API
- Different ONAP projects for respective java SDK, if any
- ONAP CLI uses REST API to communicate with ONAP, so it depends on the ONAP API documentation project
- Integration project (CI & docker) would depends on this project ONAP CLI for automation
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing etc.
Resources:
- Primary Contact Person
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
...