1. 19 Jun, 2018 1 commit
  2. 14 Jun, 2018 1 commit
  3. 13 Jun, 2018 1 commit
  4. 10 Jun, 2018 1 commit
  5. 09 Jun, 2018 1 commit
  6. 08 Jun, 2018 1 commit
  7. 07 Jun, 2018 1 commit
  8. 29 May, 2018 1 commit
  9. 25 May, 2018 2 commits
  10. 15 May, 2018 1 commit
  11. 11 Apr, 2018 1 commit
  12. 10 Apr, 2018 1 commit
  13. 06 Apr, 2018 2 commits
  14. 05 Apr, 2018 5 commits
  15. 04 Apr, 2018 1 commit
  16. 30 Mar, 2018 1 commit
  17. 23 Mar, 2018 2 commits
  18. 20 Mar, 2018 1 commit
  19. 18 Mar, 2018 1 commit
  20. 12 Mar, 2018 2 commits
  21. 09 Mar, 2018 1 commit
  22. 06 Mar, 2018 1 commit
  23. 05 Mar, 2018 1 commit
    • Support CloudFoundry out of the box · 80eaf615
      Tetsushi Awano authored
      This commit enables client and server to work out of the box on
      CloudFoundry.
      The client derives the registration info (url and metadata) from the
      VCAP environment variables.
      The server computes a unique instanceId and the correct headers for the
      cf router based on the metadata provided by instances. Also suppots the
      CloudFoundry discovery client ootb.
      
      closes #434
  24. 02 Mar, 2018 1 commit
  25. 20 Feb, 2018 1 commit
  26. 19 Feb, 2018 1 commit
  27. 16 Feb, 2018 1 commit
  28. 05 Feb, 2018 1 commit
  29. 04 Feb, 2018 1 commit
  30. 01 Feb, 2018 1 commit
  31. 20 Jan, 2018 1 commit
  32. 04 Jan, 2018 1 commit
    • Refresh info when registration has changed. · fa35de89
      Johannes Edmeier authored
      The info should be updated when the registration has changed. In order
      to prevent a stale instance info, the sba client includes a "startup"
      timestamp in the metadata as default. So when the instance is restarted
      the registration changes and the info is updated, even when the instance
      isn't considered as down in between.
      
      To prevent this when using a discovery client you need to add a value
      to the metadata which changes with every restart.
      (e.g. `random=${random.value}`)
      
      fixes #556