Now that the Person credential is available for public use, it is legitimate for developers to want to execute proof-requests using it in the lower environments to validate their code without having to design and issue test credentials matching the Person schema.
CANdy prod should be added in read-only mode to the following environments:
[x] dev: add to this environment first and complete validation that no adverse side effects appear in the system.
[x] test
[x] sandbox: changes will roll-out on the next deployment
It should be possible to just add the CANdy Prod configuration to the ledgers file (omitting the endorser keys/settings) and validate it is possible to complete proof-requests targeting production credentials, but nothing else with the production ledger.
Now that the Person credential is available for public use, it is legitimate for developers to want to execute proof-requests using it in the lower environments to validate their code without having to design and issue test credentials matching the Person schema.
CANdy prod should be added in read-only mode to the following environments:
dev
: add to this environment first and complete validation that no adverse side effects appear in the system.test
sandbox
: changes will roll-out on the next deploymentIt should be possible to just add the CANdy Prod configuration to the ledgers file (omitting the endorser keys/settings) and validate it is possible to complete proof-requests targeting production credentials, but nothing else with the production ledger.