Yang errors fixes:

- fixed keys
- restored 'config true' state in references
- changed 'config false' to 'true' in subject-feature-definitions

Change-Id: Idc509de204d72d4db30f26a0048ecd9fb3ed00c8
Signed-off-by: Konstantin Blagov <kblagov@cisco.com>

diff --git a/groupbasedpolicy/src/main/yang/model/policy.yang b/groupbasedpolicy/src/main/yang/model/policy.yang
index 53a5a8c9f29817671f9faa51be9cba6c7693779a..5f3e864654b5519b06140cd8935f6bee36ea03d7 100755 (executable)
--- a/groupbasedpolicy/src/main/yang/model/policy.yang
+++ b/groupbasedpolicy/src/main/yang/model/policy.yang
@@ -524,6 +524,7 @@ module policy {
                 "A reference to an action defined in the subject 
                  feature instances for the tenant.";
 
+            key name;
             leaf name {
                 description "The name of the action instance";
                 type leafref {
@@ -634,7 +635,7 @@ module policy {
              MAY instead apply the parent subject feature and instead
              raise a nonfatal exception.";
 
-        config false;
+        config true;
 
         list classifier-definition {
             description
@@ -1321,13 +1322,15 @@ module policy {
                      tenant, and provider matchers will apply against
                      capabilities and conditions in the referenced
                      tenant.";
-                
+
+                key contract-id;
+
                 leaf tenant-id {
                     description
                         "The tenant ID of the tenant containing the 
                          contract.";
                     type leafref {
-                        path "/tenants/tenant/contract/id";
+                        path "/tenants/tenant/id";
                     }
                 }
                 leaf contract-id {