- Increment the version, set SHR_VERSION in the shr api project.
- Increment the version of the dependent projects:
- shr client
- shr datasense
- patient journal
SHR can now be exposed under two urls:
Latest SHR
http:shr_host:shr_port/path/to/end-point --> default url
http:shr_host:shr_port/version/path/to/end-point --> versioned url
- If a new version is released, the older version need not serve the default url.
To achieve this clear out the IS_LATEST_SHR property of SHR Service
set SHR_VERSION=v1
Older SHR
http:shr_host:shr_port/v1/path/to/end-point
- By default clients, point to the latest shr. However if versioned shr services are maintained, clients can still point to an earlier version.
- Version configuration placeholders are present in the respective property files for each project, where version can be updated.
| client property | name |
|---|---|
| bdshr client | shr.version |
| datasense | SHR_VERSION |
| patient journal | SHR_VERSION |
This way, only clients who are strict about sticking to an older version have to update their properties to point to the older version.Else auto point to the latest version
- Update the markers table to point to the updated version.Set up reverse proxy configuration mapping the default url to the latest api releaseolder version for the sync to continue.