11:27 a.m.
I am working in my own branch, but am about to introduce resource configuration and
operations to the resource type metadata. This was in part due to the UI folks needing the
hostname to show in the GUI.
I wanted to let people know what this looks like - speak now if you see problems.
The resourceType will now have as part of its attached metadata a list named
"resourceConfiguration" which consists of config property types (today, there is
only "name" associated with resource config property types, but you can envision
other things like "dataType" (for boolean, integers, etc)).
There is also a list of operations (today, consists of only a name and optional
"operationName").
The JSON for resourceType looks like this inside inventory (this is for the top level
"WildFly Server" type):
"tenant": "28026b36-8fe4-4332-84c8-524e173a68bf",
"id": "WildFly Server",
"version": "0.1",
"properties":
{
"name": "WildFly Server",
"operations":
[
{
"name": "Reload Server",
"operationName": "reload"
}
],
"resourceConfiguration":
[
{
"name": "Hostname"
},
{
"name": "Max Heap"
},
{
"name": "Version"
}
]
}
A resource of this type would look like:
"tenant": "28026b36-8fe4-4332-84c8-524e173a68bf",
"environment": "test",
"feed": "mazztower",
"id": "[Local Host~/]",
"type": <<<what I showed above>>>,
"properties":
{
"name": "WildFly Server [Local Host] [mazztower]",
"resourceConfiguration":
[
{
"name": "Version",
"value": "8.2.0.Final"
},
{
"name": "Hostname",
"value": "mazztower"
},
{
"name": "Max Heap",
"value": "477626368"
}
]
}