Update patch set 1

Patch Set 1:

(1 comment)

Patch-set: 1

e2e560642af96107b93872b0c0072b66c0658dab

@@ -70,6 +70,30 @@
       "revId": "e2e560642af96107b93872b0c0072b66c0658dab",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": false
+    },
+    {
+      "key": {
+        "uuid": "3a7e1126_077dd3e6",
+        "filename": "manifests/logging.pp",
+        "patchSetId": 1
+      },
+      "lineNbr": 1,
+      "author": {
+        "id": 9914
+      },
+      "writtenOn": "2015-12-17T21:10:51Z",
+      "side": 0,
+      "message": "I can certainly do that, but I need a little clarification as to how all this is supposed to work.\n\nI noticed that the logging.pp file does not have any of the \"pick\" logic that would select either a parameter from\n::barbican::api::foo or $foo.\n\nIs the idea here then that my barbican::api resource would NOT contain parameters for logging.  Rather my manifests would define a barbican::api::logging resource -\u003e ::barbican::api resource  ?\n\nIf not, how do these parameters get passed from the barbican::api to barbican::api::logging?\n\nWhat is the expected way to do this?",
+      "parentUuid": "3a7e1126_199c6fbf",
+      "range": {
+        "startLine": 1,
+        "startChar": 18,
+        "endLine": 1,
+        "endChar": 25
+      },
+      "revId": "e2e560642af96107b93872b0c0072b66c0658dab",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": false
     }
   ]
 }