1. 30 Jun, 2017 1 commit
  2. 29 May, 2017 1 commit
  3. 23 May, 2017 1 commit
    • Angus Lees's avatar
      Accept a wider range of jsonnet result structures · e1285841
      Angus Lees authored
      There is some variation in jsonnet "result" conventions.  This change
      assumes the top level is a JSON object, and then walks down looking
      for objects with `apiVersion` & `kind` fields.
      
      While walking down, the current code will expand JSON arrays, and
      object values.
      
      In particular, this should correctly accept:
      - single-value JSON files
      - arrays (jsonnet --yaml-stream)
      - "filename->object" objects (jsonnet --multi)
      
      (Note that any v1.Lists encountered are still expanded in a
      second-pass, as before)
      e1285841
  4. 18 May, 2017 1 commit
    • Angus Lees's avatar
      Implement "update" subcommand · d0327629
      Angus Lees authored
      - Support the standard client-go/kubectl flags
      - Switch object types to use client-go rather than apimachinery
      - Implement update subcommand
      d0327629
  5. 16 May, 2017 2 commits
    • Angus Lees's avatar
      gofmt · 4ab98f60
      Angus Lees authored
      4ab98f60
    • Angus Lees's avatar
      Add ability to read json/yaml/jsonnet input files · 9ddea438
      Angus Lees authored
      File format is recognised via simple file extension check.
      
      Any "List" objects found will be expanded into their constituent
      items, so single-element formats like json and jsonnet can use a
      v1.List to capture multiple resource objects.
      9ddea438