> For the complete documentation index, see [llms.txt](https://divoc.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divoc.digit.org/divoc-wiki-3.1/platform/release-notes/divoc-2.0-release-features.md). # DIVOC 2.0 Release Features ## Version release date * March 25, 2022. ## **Release summary** If your country is implementing DIVOC 2.0, it is important to know the additions/changes that we have made as part of this release: * **Configuration management via** [**etcd**](https://etcd.io/)**:** You can make configuration changes to DIVOC’s certificate module via etcd without needing a new deployment. Click [**here**](/divoc-wiki-3.1/platform/configuration/configuration-management-via-etcd.md) to know more. * **Support for EU compliant digital certificates and Smart Health Cards:** DIVOC’s **EU-DCC** and **SHC** adapter services facilitate easy travel for residents from DIVOC’s adopter countries. Know more about DIVOC’s [**EU-DCC**](/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-2.0/divocs-eu-dcc-adapter-service.md) and [**SHC**](/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-2.0/divocs-shc-adapter-service.md) adapter services. * **Print certificates at the facility:** We have added the capability to print vaccination certificates when a beneficiary walks into a facility. Click [**here**](/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-2.0/printing-certificates-at-a-facility.md) to know more. * **New API for revocation services:** A new Revoke API has been introduced that can be used to revoke an issued certificate for manual revocation use cases. Click [**here**](/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-2.0/revoking-a-divoc-certificate.md) to know more. * **Deployment activities automated reducing installation time:** \- Automating our infrastructure setup has reduced our deployment time from about 3 days to 1 day. \- DIVOC’s [**installation process**](/divoc-wiki-3.1/platform/installation/setting-up-divoc-in-k8-cluster/how-to-install-divoc.md) has been streamlined with the introduction of the new scripts. The details of the scripts are given below: 1. Install the prerequisites and set up the various hardware clusters. 2. Push the docker images to the appropriate registry. 3. Deploy the code from the registry into the Kubernetes cluster. * **Enhanced performance of PDF certificate generation:** We have fine-tuned our PDF generating algorithms, which has lowered the consumption of system resources. [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://divoc.digit.org/divoc-wiki-3.1/platform/release-notes/divoc-2.0-release-features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.