Address a few pieces of feedback from @ensonic

[mattmoor]

Removes some of the friction from: #68
Fixes: #69

[mattmoor]

@ensonic This should enable you to use a much more relaxed set of things as the keys in the images dictionary. It isn't completely free-form because it still becomes a suffix of the image name, but I also disable strictness, so things like tags can be inferred.

If you could take this for a spin, and LMK what you think I'd appreciate it :)

[mattmoor]

@ensonic Were you able to make this work?

[ensonic]

I don't need to prefix my rule names anymore. Thanks. But we still have a problem.
BUILD:

k8s_object(
    name = "deployment",
    template = ":deployment.yaml",
    images = {
      "web-frontend": "//src/docker/web_frontend:web_frontend",
    },
  )

deployment.yaml

apiVersion: extensions/v1beta1
kind: Deployment
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: web-frontend
        image: web-frontend 

Since you are using a simple expand_template action and the substitution keys are simple words, this will replace web-frontend in both name and image. What you want is to use the name as the name and not require the images key to be a valid image name.

[mattmoor]

@ensonic LOL, yeah this was one of my original motivations for sticking with strict image names. I'm not sure how to avoid it without some level of schema-awareness.

[ensonic]

Yeah, it is tricky. We should merge this. I've filed a new ticked to discuss the expansion:
#83