Created
September 21, 2012 15:15
-
-
Save kabir/3762099 to your computer and use it in GitHub Desktop.
Core resource model comparison
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| STANDALONE | |
| ====== Comparing core models ====== | |
| ====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.4.0 ======= | |
| --- Problems for relative address to root []: | |
| Missing attributes in current: [profile-name]; missing in legacy [running-mode] | |
| >>> Legacy was wrong - profile name was only used in domain servers, DP made no distinction | |
| Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'nillable' for parameter 'runtime-name' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>>> Legacy was wrong, op handler allows for null | |
| Missing parameters for operation 'replace-deployment' in current: []; missing in legacy [content] | |
| >>> Legacy was wrong, content is not required if replacing with an existing deployment | |
| --- Problems for relative address to root ["core-service" => "service-container"]: | |
| Different 'type' for 'reply-properties' for operation 'dump-services'. Current: undefined; legacy: STRING | |
| --- Problems for relative address to root ["deployment" => "*"]: | |
| Missing value-type for attribute 'content' in current: [bytes, input-stream-index, url]; missing in legacy [] | |
| >>>> Legacy was wrong. These missing attributes are used in ops but not in the resource. The values for these in resource become the hash | |
| Different 'nillable' for value-type key 'path' for attribute 'content'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'archive' for attribute 'content'. Current: true; legacy: false | |
| Different 'nillable' for attribute 'enabled'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'add'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'add'. Current: true; legacy: false | |
| Different 'nillable' for parameter 'enabled' of operation 'add'. Current: true; legacy: false | |
| >>> For these ^^ Legacy was wrong, it may be null - validation picks up correct combinations | |
| --- Problems for relative address to root ["system-property" => "*"]: | |
| Different 'nillable' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for null | |
| Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for expressions | |
| ====== Comparing subsystem models ====== | |
| -- SNIP -- | |
| Done comparison! | |
| HOST | |
| ====== Comparing core models ====== | |
| ====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.4.0 ======= | |
| <tomaz> | |
| --- Problems for relative address to root []: | |
| Different 'type' for value-type key 'port' for value-type key 'remote' for attribute 'domain-controller'. Current: INT; legacy: STRING | |
| >>> Legacy was wrong | |
| Different 'expressions-allowed' for value-type key 'port' for value-type key 'remote' for attribute 'domain-controller'. Current: false; legacy: true | |
| >>>> I think we support expressions here??? i.e. legacy is wrong | |
| Different 'expressions-allowed' for value-type key 'host' for value-type key 'remote' for attribute 'domain-controller'. Current: false; legacy: true | |
| >>>> I think we support expressions here??? i.e. legacy is wrong | |
| Different 'nillable' for value-type key 'remote' for attribute 'domain-controller'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'nillable' for value-type key 'local' for attribute 'domain-controller'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'storage' for attribute 'domain-controller'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'management-major-version'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'management-micro-version'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'management-minor-version'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'nillable' for attribute 'master'. Current: true; legacy: false | |
| >>>> It now has a default of false | |
| Different 'storage' for attribute 'master'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'namespaces'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'product-name'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'product-version'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'nillable' for attribute 'release-codename'. Current: true; legacy: false | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'release-codename'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'nillable' for attribute 'release-version'. Current: true; legacy: false | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'release-version'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'storage' for attribute 'schema-locations'. Current: "configuration"; legacy: "runtime" | |
| >>>> It is configuration | |
| Different 'nillable' for attribute 'server-state'. Current: true; legacy: false | |
| >>>> This attribute is a no-op, it is undefined now, and was in master before this change and in 7.1.2 | |
| Different 'type' for parameter 'port' of operation 'write-remote-domain-controller'. Current: INT; legacy: STRING | |
| >>>> Legacy was wrong | |
| --- Problems for relative address to root ["server-config" => "*","system-property" => "*"]: | |
| Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false | |
| >>>> it now has a default of true | |
| Different 'nillable' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for null | |
| Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were resolving expressions | |
| --- Problems for relative address to root ["system-property" => "*"]: | |
| Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false | |
| >>>> it now has a default of true | |
| Different 'nillable' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for null | |
| Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were resolving expressions | |
| ====== Comparing subsystem models ====== | |
| Done comparison! | |
| DOMAIN | |
| ====== Comparing core models ====== | |
| ====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.4.0 ======= | |
| --- Problems for relative address to root []: | |
| Missing attributes in current: []; missing in legacy [launch-type] | |
| >>> Legacy was wrong | |
| Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>> Legacy was wrong | |
| Different 'nillable' for parameter 'runtime-name' of operation 'full-replace-deployment'. Current: true; legacy: false | |
| >>>> Legacy was wrong, op handler allows for null | |
| --- Problems for relative address to root ["deployment" => "*"]: | |
| Missing value-type for attribute 'content' in current: [bytes, input-stream-index, url]; missing in legacy [] | |
| >>>> Legacy was wrong. These missing attributes are used in ops but not in the resource. The values for these in resource become the hash | |
| Different 'nillable' for value-type key 'path' for attribute 'content'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'archive' for attribute 'content'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'add'. Current: true; legacy: false | |
| Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'add'. Current: true; legacy: false | |
| >>> For these ^^ Legacy was wrong, it may be null - validation picks up correct combinations | |
| --- Problems for relative address to root ["profile" => "*"]: | |
| Different 'type' for attribute 'name'. Current: STRING; legacy: undefined | |
| >>> Legacy was wrong | |
| --- Problems for relative address to root ["server-group" => "*","deployment" => "*"]: | |
| Different 'nillable' for attribute 'enabled'. Current: true; legacy: false | |
| >>>> It is now nillable with a default of true | |
| Missing parameters for operation 'add' in current: [content]; missing in legacy [] | |
| >>>> Legacy was wrong - ServerGroupDeploymentAddHandler requires content | |
| Different 'nillable' for parameter 'enabled' of operation 'add'. Current: true; legacy: false | |
| >>>> It is now nillable with a default of true | |
| --- Problems for relative address to root ["server-group" => "*","system-property" => "*"]: | |
| Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false | |
| >>>> it now has a default of true | |
| Different 'nillable' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for null | |
| Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were resolving expressions | |
| --- Problems for relative address to root ["system-property" => "*"]: | |
| Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false | |
| >>>> it now has a default of true | |
| Different 'nillable' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were allowing for null | |
| Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false | |
| >>> Legacy was wrong - the existing add + write handlers were resolving expressions | |
| ====== Comparing subsystem models ====== | |
| Done comparison! |
@bstansberry ["core-service" => "service-container"]: problem was there as part of my commit that was not suppose to go to phase1...
tnx for the fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
--- Problems for relative address to root ["core-service" => "service-container"]:
Different 'type' for 'reply-properties' for operation 'dump-services'. Current: undefined; legacy: STRING
I think legacy was correct.