Blueprint examples in Blueprints Catalog widget not up to date
Blueprints Catalog widget in Cloudify Catalog page uses http://repository.cloudifysource.org/cloudify/blueprints/4.4/examples.json file as a base to present list of blueprint examples to the user.
All the examples in that file are taken from https://github.com/cloudify-examples/ we can see:
So it is written there that we should use use https://github.com/cloudify-community/blueprint-examples .
Steps to Reproduce
OS (CLI), HA cluster, cloud provider
Steps to reproduce:
Why Propose Close?
It is a file hosted in s3. I’m not sure how I could chnage the HTTP headers that they are sending?
Can you add some HTTP headers to GET response on http://repository.cloudifysource.org/cloudify/blueprints/5.0.5/examples.json ? I would need probably the same as for http://repository.cloudifysource.org/cloudify/wagons/plugins.json - all 3 starting from Access-Control-* as right now that file is downloaded by client-side.
According to what Trammell mentioned - yes, I think the solution for the future (post-5.0.5) should be to use GitHub API and fetch all the data from releases pages. Implementation should not be very hard, but we need to decide how to expose it to the user (in widget configuration). Second thing would be to develop a way of updating it before release (because the endpoint/link should provide list of blueprints examples working with specific release.
I think that it is worth to mention here that we are using similar solution (JSON file) in Plugins Catalog: http://repository.cloudifysource.org/cloudify/wagons/plugins.json
Don’t we need to provide list of plugins per version as well? Right now we are providing the same list of plugins for different Cloudify versions.
thanks for the fast response , please open a Jira to commit it in one of the repos and copy it to s3 as a part of the build.
Can you take it from here ? (should be an easy fix)
I also updated here, where we can manage it. Although I think recommends that we just read the available examples from our release pages.