venafi-integration-core 2.2.0 → 2.3.0

package/bundle.mjs

@@ -32604,6 +32604,26 @@ kubectl logs -f <satellite-pod> -n satellite
 
 **Key diagnostic**: If the satellite gets an access token after a discovery run but machine identities never appear in the UI, the connector response was accepted by the satellite but rejected by the platform. Check \`GET /v1/machines/{id}/discovery\` for \`errorCount > 0\`.
 
+**Tip: Connector logs in satellite output**: The satellite streams connector pod logs through its own log output. Even after a connector pod has scaled to zero and its logs are gone, you can find them in the satellite logs by grepping for \`"plugin":\`:
+
+\`\`\`bash
+kubectl logs <satellite-pod> -n satellite | grep '"plugin":'
+\`\`\`
+
+### Knative Revision Naming
+
+When the platform deploys a connector, it creates a Knative service (ksvc) with an immutable revision. If you need to manually patch a ksvc (e.g., to change env vars or image for debugging), you **must include a new revision name** \u2014 Knative rejects spec changes without a name change:
+
+\`\`\`bash
+# This will FAIL \u2014 "saw the following changes without a name change"
+kubectl patch ksvc <name> -n plugins --type merge -p '{"spec":{"template":{"spec":{"containers":[{"image":"new-image"}]}}}}'
+
+# This WORKS \u2014 include a new revision name
+kubectl patch ksvc <name> -n plugins --type merge -p '{"spec":{"template":{"metadata":{"name":"<name>-debug-001"},"spec":{"containers":[{"image":"new-image"}]}}}}'
+\`\`\`
+
+Note: Manual ksvc patches are for debugging only. The satellite routes to the revision from the last \`req.plugin.deploy\` command, so manually created revisions won't receive traffic from Venafi Cloud workflows. For normal development, use the standard \`make push\` \u2192 \`make manifests\` \u2192 PATCH \u2192 Test Connection flow.
+
 ### Debugging Discovery Results via API
 
 \`discoveryStatus: COMPLETED\` does NOT mean certificates were stored. It only means the workflow finished. The platform silently rejects malformed certificates.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "venafi-integration-core",
-  "version": "2.2.0",
+  "version": "2.3.0",
   "description": "MCP server providing shared knowledge, templates, and tools for building Venafi integrations (connectors and adaptable drivers)",
   "main": "bundle.mjs",
   "type": "module",