-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify/Group the different required CAMP input models #19
Comments
This is indeed the case. We should try to consolidate the input. Current input files are features.yml, images.yml, composite.yml, variables.yml (in some use cases). |
also see #11 |
This should be better in v0.2, which consumes only a single input file. See the documentation of the CityGo case study. I thus close this issue, but feel free to reopen or open another issue should you have any other problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Characteristics
Description
Current CAMP tool requires a number of related input models for describing the configuration amplification application domain, including features.yml, images.yml, genimages.yml, composite.yml, variables.yml, etc.
Managing all these models, and providing new instances for different application domains could be complex due to the fragmentation of the CAMP input model across all these models.
We recommend to group all these modeling aspects (features, images, variables, etc) within different subsection of a common CAMP input model (i.e. camp.yml)
Steps to reproduce
N/A
Other files and URLs
Relationships
See #18 and #14
Help on issue template
Preview to follow the link or open file .github/ISSUE_DOC.md
The text was updated successfully, but these errors were encountered: