Closed lzbj closed 7 years ago
@lzbj I suggest we separate this issue into small issues, then it will be easier to manage. e.g.
By the way, I'm think about proposing PR with manifest and deployment files to each repo if the use case has its own repo. For example, we can provide a PR to openwhisk-package-rss repo to add manifest.yml and deployment.yml other than moving the source code of openwhisk-package-rss to our repo. We can also propose a PR to openwhisk-catalog to add manifest and deployment files to the packages in catalog.
Or maybe we add a sample folder and add all manifest and deployment there and link to the source code of each use case repo, if our wskdeploy supports link to other github repo.
@daisy-ycguo, please open new issues if you think we'd better do, we can discuss with others later.
Do we need to add both deployment and manifest files? I think we just need to add a manifest file to the repos. In our current model, the deployment file is just used for deployment instances.
@daisy-ycguo @pritidesai please open issues if you need to add more real word app usecases, as we already have a lot of test cases, so I'll close this one.
Lets discuss this in today's scrum meeting and than open issues accordingly.
Now the use cases contains sample ones, we need support real and more complex openwhisk packages use cases such as https://github.com/openwhisk/openwhisk-package-rss Github feed advanced, polygen tracking etc mentioned in the specification.