Infrahub - v1.0.10

Release 1.0.10

This release is a bug-fix release 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.

Added

• Make URL fields clickable in the details view (#5005)

Fixed

• Support directionality in the query to get all peer IDs for a given group of nodes (#3065)
• Fix errors when executing infrahub db update-core-schema command that were impacting migrations from prior versions (#5186, #5254)

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.0.10"; 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.

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

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

Infrahub - v1.0.9

Release 1.0.9

This release is a bug-fix release to resolve issues found in Infrahub v1.0.8 and prior.

Main changes

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

Added

• Adding invoke tasks to assist with release process. (#4519)
• Add pagination and backend search in new combobox for relationships.
• Added custom Towncrier template to remove extra space after new Changelog entries.
• In schema viewer, we now display Hierarchical value for generics.

Fixed

• Update delete constraints to correctly account for relationships on generics and relationships for which the peer kind is a generic. (#4332)
• Fix error when pool was used a relationship name. (#4807)
• Ensure that deleted schema nodes are removed from all workers and that the schema is in sync without having to restart. (#4836)
• Consistently use "Save" on all object forms submit buttons. (#4850)
• Search shortcuts show Cmd on macOS and Ctrl on other systems. (#4861)
• Update the parent relationship query to populate the dropdown options when editing an object, ensuring the current parent is correctly selected for the current node. (#5035)
• Correctly refresh menu after access token has expired. (#5099)
• On the object permission form, fix the name option selection when changing the namespace to get the latest options and to be able to choose a name option. (#5100)
• Prevent adding a new mandatory attribute or relationship to the schema if some nodes are already present in the database. (#5106)
• Refresh branch hash on local worker during branch create. (#5130)
• Fix uniqueness constraint check with enum based attributes. (#5132)
• Editing old CHANGELOG.md entries to use uniform formatting from new Towncrier template.
• Store CoreProfile in database to ensure consistent initial schema hash. Prior to this the schema was reported as being out of sync when starting the application for the first time. This error wouldn't have hade any impact but was confusing. The workaround would be to load a schema or restart the application at least once after first time initialization.
• Use the branch uuid instead of the internal database id to track the hash of the schema in the cache.

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.0.9"; 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.

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

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

Infrahub - v1.1.0b2

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.

Infrahub - v1.0.8

Release 1.0.8

This release is a bug-fix release to resolve issues found in Infrahub v1.0.7 and prior.

Main changes

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

Added

• Add sso_user_default_group security setting to provide the name of a group to which SSO users will be assigned if the identity provider does not gives a list of groups to use (#4924)
• Added a 'append_git_suffix' configuration setting for Git repositories that allows you to define domains for auto appending '.git' to repositories defined with an HTTP URL (#5077)

Fixed

• Loosened up logic to determine when an artifact needs to be regenerated during a proposed change. This is to ensure that we always generate a new artifact if required. Until some other parts are refactored this will also need that we will generate artifacts in a few situations where it's not strictly required. This last part is a temporary solution. (#4198)

• Migrates from headless UI combobox to cmdk to resolve focus behavior issues when there is no result in the search anywhere (#4715)

• Fix GraphQL mutations to make user permissions updates work correctly

  • Update the alert message to better reflect the changes (between creation and update)
  • Fix the objects delete modal on the global permission view
  • Fix the global permission update mutation

  (#4881, #4952)

• Validate that a deleted schema node is not used in any relationship when loading a new schema (#4912)

• Set content type of artifact when rendered to fix artifact content type if artifact definition has changed (#4969)

• Raise error if pool allocation misses data to create node (#5006)

• Process new schema before replacing branch in registry to avoid causing the GraphQL schema to be generated while the new schema is still loading (#5008)

• Added a check on repository import and sync to wait until the schema has converged before importing additional objects when the repository contains an updated schema (#5051)

• Fix artifact definition targets when changed in repository so that it's reflected in the database (#5060)

• GraphQL query with filters on attribute of type List return the expected result (#5091)

• Prevent adding a new mandatory attribute or relationship to the schema if some nodes are already present in the database (#5106)

• Ensure that permission queries are run in non isolated mode so that updates from the default branch are automatically reflected in other branches (#5110)

• Add retry for transient database errors during IP reconciliation tasks

• Corrected configuration for prefect worker to never prompt for Git credentials on the console

• Fix artifact object relationship by enforcing it to be an artifact target

• Fix bug in IP reconciliation query around deleted nodes and relationships

• Fix issue that could cause diff generation to crash if a schema was renamed

• Fixes a bug that prevented running a generator from a read-only repository

• Generator groups are correctly created after merging a proposed change

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.0.8"; 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.

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

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

Infrahub - v1.1.0b1

Release 1.1.0 Beta 1

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.7 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)

Fixed

• Fix search anywhere so it looks at Groups (#3173)
• Loosened up logic to determine when an artifact needs to be regenerated during a proposed change. This is to ensure that we always generate a new artifact if required. Until some other sections are refactored this will also mean that Infrahub will generate artifacts in a few situations where it's not strictly required. This last part is a temporary solution. (#4198)
• Use the repository object ID as name for its git working copy directory (#4296)
• Search anywhere now supports IPv6 extended format (#4613)
• Synchronise git repository clones and updates for task workers in order to remove the need for a shared storage (#4789)
• 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)
• 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 the api/diff/artifacts endpoint to use a dedicated query

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.

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

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

Infrahub - v1.0.7

Release 1.0.7

This release is a bug-fix release to resolve issues found in Infrahub v1.0.6 and prior.

Main changes

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

Fixed

• Fix permission issue with Repository management (#4976)
• Fix bug that prevented setting an attribute to NULL as part of a merge (#4996)
• Fix a bug in the query to delete a relationship that could create unnecessary "deleted" edges on the database
• Fix bug in incremental diff addition for nodes within a hierarchy

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.0.7"; 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.

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

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

Infrahub - v1.0.6

Release 1.0.6

This release is a bug-fix release to resolve issues found in Infrahub v1.0.5 and prior.

Main changes

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

Fixed

• Forbid changing the "optional" property of an inherited attribute to not break GraphQL schema generation (#4936)
• Permission edit_default_branch is now enforced properly when loading a schema (#4958)
• Session is now correctly cleared when logging out from the web UI (#4962)
• Anonymous user will get a 401 response when trying to load a schema

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.0.6"; 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.

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

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

Infrahub - v1.0.5

Release 1.0.5

This release is a bug-fix release to resolve issues found in Infrahub v1.0.4 and prior.

Main changes

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

Fixed

• Node attribute name can now be type (#4381)

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.0.5"; 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.

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

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

Infrahub - v1.0.4

Release 1.0.4

This release is a bug-fix release to resolve issues found in Infrahub v1.0.3 and prior.

Main changes

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

Fixed

• Profiles now have a Human-Friendly Identifier (HFID) defined based on profile_name (#4758)
• Workers out of sync after deleting node from schema ([#4836])
• Infrahub returns a proper error message when trying to load a schema with generic with the same Kind as an existing node (#4837)
• Default to using HTTP GET for UserInfo endpoints (OAuth2/OIDC) (#4898)
• Remove Profile in registry for renamed schema nodes (#4909)

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.0.4"; 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.

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

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

Infrahub - v1.0.3

Release 1.0.3

This is a bug-fix release to address issues found in Infrahub v1.0.2.

Main changes

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

Fixed

• Fix hierarchical schema update logic to correctly update peer on parent relationship of new node (#4838)
• Fix hierarchical schema update logic to correctly update peer on parent of new child node (#4839)
• Define the version of numpy to install in pyproject.toml

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.0.3"; 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.

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

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