The prism components:signature command in Prism verifies the existence of the component in the Prismatic Platform before returning it. If you want the command to return a key regardless of whether the component exists or not in the API, you can run it with the skip-signature-verify option. This will allow the command to return a key even if the component is not found.
If you're using a Component Manifest with an unverified signature key in a Code Native Integration (CNI), it's fine to work with it locally. However, when you try to integrate the CNI with the Prismatic Platform, it will fail.
Other changes
Moved shared functions into the components index to indicate they are used in multiple component commands.
The
prism components:signaturecommand in Prism verifies the existence of the component in the Prismatic Platform before returning it. If you want the command to return a key regardless of whether the component exists or not in the API, you can run it with theskip-signature-verifyoption. This will allow the command to return a key even if the component is not found.If you're using a Component Manifest with an unverified signature key in a Code Native Integration (CNI), it's fine to work with it locally. However, when you try to integrate the CNI with the Prismatic Platform, it will fail.
Other changes
Moved shared functions into the components index to indicate they are used in multiple component commands.