Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7223

Allow fabric gateway uriTemplate to use {majorVersion} instead of just the full {version}

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Major
    • None
    • jboss-fuse-6.3, fuse-6.x-GA
    • Fabric8 v1
    • % %

    Description

      How to provide only the profile's major version on the gateway URL? Reading about it on the fabric guide section on fabric version we know that the gateway provide the profile version via

      {version}

      tag but this isn't desired on our scenario.


      Scenario #1:

      We need to upgrade one of the container's version profile from 1.0 to 1.1 and keep the major version on URL, for example:

      http://www.example.com/services/v1/myservice

      In this scenario, all containers on Fabric will be upgrade to profile 1.1. On minor updates, we don't want to impact our clients on a change in the URL.


      Scenario #2

      Some containers on the Fabric will be upgrade, for example, from 1.1 to 2.0. In this scenario we need to keep both versions online:

      http://www.example.com/services/v1/myservice
      http://www.example.com/services/v2/myservice

      The container's profile configuration should be:

      managed1 -> 1.1 --> http://www.example.com/services/v1/myservice
      managed2 -> 1.1 --> http://www.example.com/services/v1/myservice
      managed3 -> 2.0 --> http://www.example.com/services/v2/myservice

      Attachments

        Activity

          People

            pantinor@redhat.com Paolo Antinori
            rhn-support-rkieley Roderick Kieley
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: