laetho/metagraf

metaGraf is a opinionated specification for describing a software component and what its requirements are from the runtime environment. The mg command, turns metaGraf specifications into Kubernetes resources, supporting CI, CD and GitOps software delivery.

metagraf's Issues

--cvars does not work for JVM_SYS_PROP

Given a metagraf with

    "environment": {
      "local": [
        {
          "name": "JAVA_OPTIONS",
          "required": true,
          "type": "JVM_SYS_PROP",
          "description": "Configured Java system properties"
        },

And

    "config": [
      {
        "name": "JVM_SYS_PROP",
        "type": "JVM_SYS_PROP",
        "description": "JVM system properties",
        "options": [
          {
            "name": "my.test.prop",
            "required": true,
            "description": "test property",
            "type": "string",
            "default": "test_value"
          }
        ]
      }
    ]

I expect mg create deploymentconfig metagraf.json --cvars "my.test.prop=nissemann" --namespace cop --dryrun to populate the JAVA_OPTIONS environment like this:

              {
                "name": "JAVA_OPTIONS",
                "value": "-Dmy.test.prop=nissemann"
              },

But actual result is this:

              {
                "name": "JAVA_OPTIONS"
              },

Add support for JSONPath expressions

Proposal
mg should support JSONPath expression so we can easily fetch field data from metagraf.json without relying on other tools.
By introducing a get command that supports valid JSONPath expression we can easily and concisely rely on mg as a single tool for working with metagraf.json files.

given a metagraf.json like

{
  "kind": "MetaGraf",
  "metadata": {
    "name": "myapp",
    "annotations": {
      "my/annotation-test": "The value",
    }
  },
  "spec": {
    ...
  }
} 

When we fetch the field "name", i.e. mg get "$.metadata.name" metagraf.json
Then the value returned should be "myapp"

JVM_SYS_PROP's that are optional without value end up in environment variable.

A JVM_SYS_PROP options that is optional (not required) ends up in a generated environment variable of type JVM_SYS_PROP. It should not, unless it's configured with a value.

...
{
  "name": "JVM_SYS_PROP",
  "type": "JVM_SYS_PROP",
  "description": "JVM system properties",
  "options": [
    {
      "name": "my.property",
      "required": false,
      "description": "A property",
      "type": "string"
    },
  ]
}
...

The entry for the above property should never have generated through, mg generate properties metagraf.json:

JVM_SYS_PROP|my.property=

Make it possible to generate manifests without an k8s connection for --dryrun --output scenarios.

Investigate the possibility of generating kubernetes manifests without a connection to a kubernetes cluster when --dryrun --output arguments are passed to mg create 's.

Also investigate inspecting docker images without a docker daemon or openshift imagestream present.