Release 1.1.0 Beta 2

This is a preview release of Infrahub v1.1.0.

This release contains both new features and bug-fixes to resolve issues found in Infrahub v1.0.9 and prior.

Main changes

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

Removed

• Remove at parameter from GraphQL mutate functions (#3587)
• Remove the "role" attribute of base schema account node. This attribute was no longer useful as roles are defined as dedicated nodes and are tightly related to permissions.
• Remove the /api/diff/data and /api/diff/schema endpoints that have been replaced by the DiffTree GraphQL query

Added

• Add a "deprecation" property to attribute and relationship schema in order to allow users to identify deprecated fields for nodes and provide a user-friendly message about the deprecation reasons. (#4245)
• Add ability to use node HFID to create a related node on a generic relationship (#4649)

Changed

• Change strings referring to file system paths to pathlib.Path objects (#3545)

Fixed

• Fix search anywhere so it looks at Groups (#3173)
• Use the repository object ID as name for its git working copy directory (#4296)
• Search anywhere now supports IPv6 extended format (#4613)
• Synchronize Git repository clones and updates for task workers in order to remove the need for a shared storage (#4789)
• FIX: Resolved edge cases in 'Search Anywhere' that were causing old results to be displayed. (#4863)
• Remove Profile in registry for renamed schema nodes (#4909)
• Forbid changing the "optional" property of an inherited attribute to not break GraphQL schema generation (#4936)
• Send a request to the backend on logout to delete session cookies and prevent remaining information (#4962)
• Add support for irresolvable conflicts to the diff logic and DiffTree GraphQL query
• Fix a bug that prevented updating a relationship during a merge if ONLY the metadata was updated and not the peer.
• Fix permission check when using multiple backends, if one grants a permission the next ones must not be queried.
• Update logic to check if the changes on a branch include schema changes to use the new diff
• Update the api/diff/artifacts endpoint to use a dedicated query
• Verify if the requested branch exists. If it doesn't, it redirects to the homepage on the default branch.
  This helps avoid query issues, such as empty results (for example, an empty menu) or incorrect queries being sent.

Migration guide

The process to migrate your instance of Infrahub to the latest version may vary depending on your deployment of Infrahub.
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.

Please ensure you have a backup of your Infrahub environment prior to attempting any migration or upgrade activities.

Migration of an Infrahub instance

First, update the Infrahub version running in your environment.

Below are some example ways to get the latest version of Infrahub in your environment.

• For deployments via Docker Compose, update your container version by updating the VERSION environment variable and relaunch:
  • export VERSION="1.1.0"; docker compose pull && docker compose up -d
• For deployments via Kubernetes, utilize the latest version of the Helm chart supplied with this release

Second, once you have gotten the desired version of Infrahub in your environment, please run the following commands.

Note: If you are running Infrahub in Docker/K8s, these commands need to run from a container where Infrahub is installed.

infrahub db migrate
infrahub db update-core-schema

Finally, restart all instances of Infrahub.

Migration of a dev or demo instance

If you are using the dev or demo environments, we have provided invoke commands to aid in the migration to the latest version.
The below examples provide the demo version of the commands, however similar commands can be used for dev as well.

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.

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