Uploaded image for project: 'OpenShift Java Client'
  1. OpenShift Java Client
  2. OSJC-110

Should be able to know if a cartridge is obsolete

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 2.6.1, 2.7.0
    • 2.6.0
    • core
    • None

      OpenShift lately started to deprecate cartridges and consumers are told not to present them to the users so that users wont use outdated cartridges and they may get removed at some point in the future.

      In the current OpenShift Online you can see this by the "obsolete" property:

      "obsolete": true
      
      • full example for zend-5.6 which is superseeded by the newer zend-6.1 ("obsolete": true):
        curl -H "Accept: application/json; version=1.2" --user <USER>:<PASSWORD> https://openshift.redhat.com/broker/rest/cartridges
        {
                    "activation_time": "2014-04-08T20:30:59Z",
                    "automatic_updates": true,
                    "creation_time": "2014-04-08T20:30:59Z",
                    "description": "A PHP server by Zend for applications that require performance, reliability and security. Zend Server combined with Zend Studio offers code optimization, debugging, and code assist.",
                    "display_name": "PHP 5.3 with Zend Server 5.6",
                    "help_topics": {
                        "Developer Center": "https://www.openshift.com/developers"
                    },
                    "id": "53445c82e0b8cddcff00000d",
                    "license": "Commercial",
                    "license_url": "http://static.zend.com/topics/Zend-License-EULA-2010-09-2.pdf",
                    "maintained_by": "redhat",
                    "name": "zend-5.6",
                    "obsolete": true,
                    "supported_scales_from": 1,
                    "supported_scales_to": 1,
                    "tags": [
                        "service",
                        "php",
                        "web_framework"
                    ],
                    "type": "standalone",
                    "usage_rates": [
        
                    ],
                    "version": "5.6",
                    "website": "http://www.zend.com"
                }
        
      • full example for zend-6.1 which is superseeding zend-5.6 (no obsolete property)
        curl -H "Accept: application/json; version=1.2" --user <USER>:<PASSWORD> https://openshift.redhat.com/broker/rest/cartridges
         {
                    "activation_time": "2014-04-08T20:30:59Z",
                    "automatic_updates": true,
                    "creation_time": "2014-04-08T20:30:59Z",
                    "description": "A PHP server by Zend for applications that require performance, reliability and security. Zend Server combined with Zend Studio offers code optimization, deb
        ugging, and code assist.",
                    "display_name": "PHP 5.4 with Zend Server 6.1",
                    "help_topics": {
                        "Developer Center": "https://www.openshift.com/developers"
                    },
                    "id": "53445c82e0b8cddcff00000c",
                    "license": "Commercial",
                    "license_url": "http://static.zend.com/topics/Zend-License-EULA-2010-09-2.pdf",
                    "maintained_by": "redhat",
                    "name": "zend-6.1",
                    "supported_scales_from": 1,
                    "supported_scales_to": 1,
                    "tags": [
                        "service",
                        "php",
                        "web_framework"
                    ],
                    "type": "standalone",
                    "usage_rates": [
        
                    ],
                    "version": "6.1",
                    "website": "http://www.zend.com"
                }
        

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: