Skip to main content
Release Number0.16.1
Release DateSeptember 24th, 2024
Release CodenameBeta #5, Patch #1
Taginfrahub-v0.16.1

Release 0.16.1

We are thrilled to announce the latest release of Infrahub, version 0.16.1!

This release focuses largely on bug fixes and is driven by our Beta Test users, and as always we greatly appreciate their feedback and time!

Main changes​

The largest change in this version is the movement of the Infrahub SDK into a separate repository and package.

Documentation for the SDK remains in the main Infrahub documentation at this time.

Developers may need to take the following steps to ensure their development environment has the proper SDK in place:

git checkout develop
git pull
rm -rf python_sdk
git submodule update --init

The complete list of changes can always be found in the CHANGELOG.md file in the Infrahub Git repository.

Removed​

Added​

    • In list views, always show relationships of type "Parent."
    • In the details view of an object, hide the "Parent" relationship if the parent is the current object itself.

    (#3891)

  • Add ability to construct HFIDs from payload for upsert mutations (#4167)

  • Add HFID to schema view in the frontend (#4172)

  • Update action buttons in details view and relationships views

    • in the details view, we can edit / delete the object and manage its groups
    • in the relationships views, we can add new relationships (it replaces the "+" button at the bottom)

    (#4362)

  • Prevent the form from being closed if there are unsaved changes. (#4419)

Fixed​

  • GraphQL results when querying nodes with updated_at named attributes will now return correct values instead of null/None (#3730)

  • Loading a schema with a SchemaNode referencing an incorrect menu placement now returns a proper HTTP 422 error (#4089)

  • GraphQL mutations to update a many relationship that is required on the peer will succeed or fail with the correct error (#4124)

  • Infer human-friendly ID for a schema if it includes a uniqueness constraint of a single attribute (#4174)

  • Account for uniqueness constraints of a single attribute when validating human-friendly ID (#4181)

  • Synchronize uniqueness_constraints and unique attributes during schema processing (#4182)

  • Ensure schema uniqueness_constraints are created if they are missing and human_friendly_id has been specified for the node (#4186)

  • Deleting a node that is linked to a mandatory relationship on a generic schema will now fail with an error message (#4207)

  • Fixed incorrect consumer timeout for RabbitMQ queue infrahub.rpcs

    If you are upgrading from a previous version of Infrahub and using the provided Docker Compose files you don't have to take any additional action. However if you are using your own setup for RabbitMQ you will need to manually delete the queue yourself.

    Swap the container name and credentials to RabbitMQ if they are different in your setup:

    docker exec -it infrahub-message-queue-1 rabbitmqadmin --username infrahub --password infrahub delete queue name=infrahub.rpcs

    After this step Infrahub and the Git agents need to be restarted, when doing so the correct queue will be recreated. (#4308)

  • Add documentation links for Generator Definition and Generator Instance pages to Generator topic (#4316)

  • Hierarchical node that don't have a parent or a children defined in the schema will properly enforce that constraint (#4325)

  • Properly raise errors instead of just logging them during repository import failures so that the "sync status" gets updated even if we've caught the errors. (#4334)

  • Display label composed of an attribute of type Enum will now render correctly (#4382)

  • Removed database index in Attribute Value to attribute larger than 8167 bytes (#4399)

  • Added cancel button in repository form (#4402)

  • Fixes the tasks pagination in the proposed changes tab (#4434)

Migration guide​

To migrate your instance of Infrahub to the latest version, please run the following commands and restart all instances of Infrahub.

infrahub db migrate
infrahub db update-core-schema

If you are running in Docker these commands need to run from the container where Infrahub is installed

Migration of the demo instance​

If you are using the demo environment, you can migrate to the latest version with the following commands

invoke demo.stop
invoke demo.build
invoke demo.migrate
invoke demo.start

If you don't want to keep your data, you can start a clean instance with the following command

invoke demo.destroy demo.build demo.start demo.load-infra-schema demo.load-infra-data

All data will be lost, please make sure to backup everything you need before running this command.

The repository infrahub-demo-edge has also been updated, it's recommended to pull the latest changes into your fork.