Uploaded image for project: 'Spring XD'
  1. Spring XD
  2. XD-3392

Upgrading custom module issues

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: To Do
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2.1
    • Fix Version/s: None
    • Component/s: Stream Module
    • Labels:
      None
    • Story Points:
      0
    • Rank (Obsolete):
      9223372036854775807

      Description

      At the moment, a custom module can not be upgraded at all, it's not only a desired story, as stated in XD-2889. It's indeed a major issue, since the only way to upgrade a module is by destroying the previous version first.

      However a module can not be destroyed if it's being used in existing streams, which means there is no way (at least using shell utilities) to upgrade once spring-xd is in production. Because destroying streams is simply not an option.

      What is even more annoying, if some default configuration is included in conf folder. The module can't be upgraded unless that configuration is previously removed, which makes everything even more inconvenient, because in order to upgrade custom modules, SpringXD requires you to:

      1. Remove all streams using that module
      2. Remove existing configuration
      3. Destroy the existing module
      4. Upload the new version
      5. Re-create the previously removed configuration
      6. Re-create all destroyed streams
      7. Re-deploy all previously deployed streams.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            CalamarBicefalo José Carlos Valero Sánchez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: