Merge pull request #4816 from opsmill/bdl-20241031-1.0.1

release prep for v1.0.1

Author: lykinsbd

.yamllint.yml

@@ -10,6 +10,7 @@ ignore: |
   **/node_modules
   # https://github.com/sbaudoin/yamllint/issues/16
   /helm/templates
+  /python_sdk
 
 rules:
   new-lines: disable

CHANGELOG.md

@@ -11,6 +11,15 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang
 
 <!-- towncrier release notes start -->
 
+## [1.0.1](https://github.com/opsmill/infrahub/tree/v1.0.1) - 2024-10-31
+
+### Fixed
+
+- When a user is not logged in and the branch name is not found, hide the quick-create action and display the message: 'No branch found' ([#4801](https://github.com/opsmill/infrahub/issues/4801))
+- Fix automation to trigger generation of artifacts after merging a branch ([#4804](https://github.com/opsmill/infrahub/issues/4804))
+- Avoid sending an empty list to the load schema API on repository import if it's not required
+- Update demo environment to work with Infrahub 1.0
+
 ## [1.0.0](https://github.com/opsmill/infrahub/tree/v1.0.0) - 2024-10-30
 
 ### Removed

changelog/+9b1d29f3.fixed.md

@@ -151,6 +151,15 @@ organization where it needs to be.
 
 ## Other
 
+### New task-manager component
+
+A new component called `Task Manager` has been introduced within Infrahub, and along with this change the Git-Agent has been renamed to `Task Worker`.
+The task manager is based on Prefect, a popular workflow orchestration system.
+
+The Task Manager is used internally to improve the execution and the visibility of all background tasks.
+In future releases, we are planning to bring these additional information within Infrahub itself.
+Stay tuned for more information and more exciting features around task management in upcoming releases.
+
 ### Removed
 
 - Remove previously deprecated GET API endpoint "/api/schema/" ([#3884](https://github.com/opsmill/infrahub/issues/3884))

changelog/+fix-demo.fixed.md

@@ -0,0 +1,88 @@
+---
+title: Release 1.0.1
+---
+<table>
+  <tbody>
+    <tr>
+      <th>Release Number</th>
+      <td>1.0.1</td>
+    </tr>
+    <tr>
+      <th>Release Date</th>
+      <td>October 31th, 2024</td>
+    </tr>
+    <tr>
+      <th>Release Codename</th>
+      <td>Stockholm, Patch #1</td>
+    </tr>
+    <tr>
+      <th>Tag</th>
+      <td>[infrahub-v1.0.1](https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.0.1)</td>
+    </tr>
+  </tbody>
+</table>
+
+# Release 1.0.1
+
+This is a bug-fix release to address issues found in Infrahub v1.0.0.
+
+## Main changes
+
+The complete list of changes can always be found in the `CHANGELOG.md` file in the Infrahub Git repository.
+
+### Fixed
+
+- When a user is not logged in and the branch name is not found, hide the quick-create action and display the message: 'No branch found' ([#4801](https://github.com/opsmill/infrahub/issues/4801))
+- Fix automation to trigger generation of artifacts after merging a branch ([#4804](https://github.com/opsmill/infrahub/issues/4804))
+- Avoid sending an empty list to the load schema API on repository import if it's not required
+- Update demo environment to work with Infrahub 1.0
+
+## 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 `IMAGE_VER` environment variable and relaunch:
+  - `export IMAGE_VER="1.0.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.
+
+```shell
+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.
+
+```shell
+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.**
+
+```shell
+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.

changelog/4801.fixed.md

@@ -0,0 +1,85 @@
+---
+title: Release 1.0.2 - DEVELOPMENT
+---
+<table>
+  <tbody>
+    <tr>
+      <th>Release Number</th>
+      <td>TBD</td>
+    </tr>
+    <tr>
+      <th>Release Date</th>
+      <td>TBD</td>
+    </tr>
+    <tr>
+      <th>Release Codename</th>
+      <td>TBD</td>
+    </tr>
+    <tr>
+      <th>Tag</th>
+      <td>TBD</td>
+    </tr>
+  </tbody>
+</table>
+
+# Release 1.0.2
+
+## Main changes
+
+### Unified storage
+
+### Schema
+
+### Helm chart
+
+### Other
+
+## 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 `IMAGE_VER` environment variable and relaunch:
+  - `export IMAGE_VER="1.0.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.
+
+```shell
+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.
+
+```shell
+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.**
+
+```shell
+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.