|
| 1 | +--- |
| 2 | +title: Release 1.1.8 |
| 3 | +--- |
| 4 | +<table> |
| 5 | + <tbody> |
| 6 | + <tr> |
| 7 | + <th>Release Number</th> |
| 8 | + <td>1.1.8</td> |
| 9 | + </tr> |
| 10 | + <tr> |
| 11 | + <th>Release Date</th> |
| 12 | + <td>March 7th, 2025</td> |
| 13 | + </tr> |
| 14 | + <tr> |
| 15 | + <th>Release Codename</th> |
| 16 | + <td>Lyon, Patch #8</td> |
| 17 | + </tr> |
| 18 | + <tr> |
| 19 | + <th>Tag</th> |
| 20 | + <td>[infrahub-v1.1.8](https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.1.8)</td> |
| 21 | + </tr> |
| 22 | + </tbody> |
| 23 | +</table> |
| 24 | + |
| 25 | +# Release 1.1.8 |
| 26 | + |
| 27 | +This release brings some changes and bug-fixes to resolve issues found in Infrahub v1.1.7 and prior. |
| 28 | + |
| 29 | +## Main changes |
| 30 | + |
| 31 | +The complete list of changes can always be found in the `CHANGELOG.md` file in the Infrahub Git repository. |
| 32 | + |
| 33 | +### Changed |
| 34 | + |
| 35 | +- Improved the performance of the cypher query that saves a diff in the database. |
| 36 | +- Updated the DiffUpdate mutation to return the ID of the task when `wait_until_completion` is False. Also, the argument `wait_for_completion` under the data section is deprecated and it has been replaced with `wait_until_completion` at the root of the mutation instead to align with the format of the other mutations. |
| 37 | + |
| 38 | +### Fixed |
| 39 | + |
| 40 | +- Fixed an error in the query to count the number of peers for a given cardinality-many relationship. Existing logic could have resulted in the count being multiplied by a power of 2 if changes were made to the relationship during a merge. |
| 41 | +- Fixed the HFID format in the mutations `IPAddressPoolGetResource` and `IPPrefixPoolGetResource`. |
| 42 | +- Reduced the number of database queries we run when checking a uniqueness constraint during a node update or create mutation. Specifically in the instance that node uses a schema which inherits from a generic schema and the node schema's uniqueness constraints are contained within the generic schema's uniqueness constraints. |
| 43 | +- Removed duplicated edges that could have been added to the database during concurrent updates. |
| 44 | + |
| 45 | +## Migration guide |
| 46 | + |
| 47 | +The process to migrate your instance of Infrahub to the latest version may vary depending on your deployment of Infrahub. |
| 48 | +However, at a high-level, it will involve getting the latest version of the Infrahub code, and then performing any needed Database Migrations and Schema updates. |
| 49 | + |
| 50 | +Please ensure you have a **backup of your Infrahub environment** prior to attempting any migration or upgrade activities. |
| 51 | + |
| 52 | +### Migration of an Infrahub instance |
| 53 | + |
| 54 | +**First**, update the Infrahub version running in your environment. |
| 55 | + |
| 56 | +Below are some example ways to get the latest version of Infrahub in your environment. |
| 57 | + |
| 58 | +- For deployments via Docker Compose, update your container version by updating the `VERSION` environment variable and relaunch: |
| 59 | + - `export VERSION="1.1.8"; docker compose pull && docker compose up -d` |
| 60 | +- For deployments via Kubernetes, utilize the latest version of the Helm chart supplied with this release |
| 61 | + |
| 62 | +**Second**, once you have gotten the desired version of Infrahub in your environment, please run the following commands. |
| 63 | + |
| 64 | +> Note: If you are running Infrahub in Docker/K8s, these commands need to run from a container where Infrahub is installed. |
| 65 | +
|
| 66 | +```shell |
| 67 | +infrahub db migrate |
| 68 | +infrahub db update-core-schema |
| 69 | +``` |
| 70 | + |
| 71 | +**Finally**, restart all instances of Infrahub. |
| 72 | + |
| 73 | +### Migration of a dev or demo instance |
| 74 | + |
| 75 | +If you are using the `dev` or `demo` environments, we have provided `invoke` commands to aid in the migration to the latest version. |
| 76 | +The below examples provide the `demo` version of the commands, however similar commands can be used for `dev` as well. |
| 77 | + |
| 78 | +```shell |
| 79 | +invoke demo.stop |
| 80 | +invoke demo.build |
| 81 | +invoke demo.migrate |
| 82 | +invoke demo.start |
| 83 | +``` |
| 84 | + |
| 85 | +If you don't want to keep your data, you can start a clean instance with the following command. |
| 86 | + |
| 87 | +> **Warning: All data will be lost, please make sure to backup everything you need before running this command.** |
| 88 | +
|
| 89 | +```shell |
| 90 | +invoke demo.destroy demo.build demo.start demo.load-infra-schema demo.load-infra-data |
| 91 | +``` |
| 92 | + |
| 93 | +The repository https://github.com/opsmill/infrahub-demo-edge has also been updated, it's recommended to pull the latest changes into your fork. |
0 commit comments