Skip to content
Snippets Groups Projects
  1. Jan 08, 2018
  2. Jan 05, 2018
  3. Jan 02, 2018
  4. Dec 26, 2017
  5. Dec 25, 2017
  6. Dec 22, 2017
  7. Dec 21, 2017
  8. Dec 20, 2017
  9. Dec 19, 2017
    • Alex Clemmer's avatar
      Merge pull request #245 from hausdorff/parsing-tests · 01437d9a
      Alex Clemmer authored
      Test all branches of GH URI-parsing code
    • Alex Clemmer's avatar
      Test all branches of GH URI-parsing code · d54aeb39
      Alex Clemmer authored
      When a user adds a registry (e.g., through a command like `ks registry
      add`, or implicitly through `ks init`) we must parse a URI pointing at
      registry hosted on github.com, since we currently only support the
      `"github"` protocol.
      
      This logic is somewhat complex, since we must
      
        1. infer the location of a `registry.yaml` file given the URI, and
        2. accept and parse a broad set of URIs a user might provide.
      
      For example, consider the following valid URIs, and what we do to infer
      the location of the `registry.yaml` file that specifies a registry:
      
        URIs with an explicit `registry.yaml`:
          github.com/exampleOrg/exampleRepo/blob/master/registry.yaml
          github.com/exampleOrg/exampleRepo/blob/master/incubator/registry.yaml
      
        URIs with an implicit `registry.yaml`:
          github.com/exampleOrg/exampleRepo/
          github.com/exampleOrg/exampleRepo/tree/master
      
        URIs with different protocols (or no protocol specified)
          github.com/exampleOrg/exampleRepo
          http://github....
      d54aeb39
  10. Dec 15, 2017
  11. Dec 13, 2017
  12. Dec 12, 2017
  13. Dec 11, 2017
  14. Dec 04, 2017
  15. Dec 03, 2017