Our new process using ccadb2onecrl has state being stored at Remote Settings, not both there and in this Git repo. The exceptions.json file is no longer needed.
Use of the tooling to push an exceptional revocation does not in any way require a full exceptions.json file, so when it's removed, we should update the usage documentation to simply directly interact with the Remote Settings instance.
Our new process using
ccadb2onecrlhas state being stored at Remote Settings, not both there and in this Git repo. The exceptions.json file is no longer needed.Use of the tooling to push an exceptional revocation does not in any way require a full
exceptions.jsonfile, so when it's removed, we should update the usage documentation to simply directly interact with the Remote Settings instance.