Forward port main into feature application management #799
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ash has been locked at 3.4.37 as in later versions `eager_validate_with` is broken. linked issue: ash-project/ash#1647 Signed-off-by: Francesco Noacco <[email protected]>
…vvvzpsu chore: update ash dependencies
Resolved an issue where the `closeButton` in the `ConfirmModal` was non-functional without an explicit `onCancel` handler Signed-off-by: Omar <[email protected]>
…e_button_fix Fix Confirm Modal `closeButton` not functional without onCancel handler
Your edgehog (created via docker compose) can now be exposed on an arbitrary domain, making it possible for devices in the same subnet to interact with it. Signed-off-by: Mattia Mazzucato <[email protected]>
As per deprecation notice, the version field is obsolete and will be ignored. Remove it. Signed-off-by: Mattia Mazzucato <[email protected]>
…ker-compose-from-outside-your-host Allow to reach your edgehog instance from outside your host
Signed-off-by: Davide Briani <[email protected]>
Use `manage_relationship` instead of `change_attribute` for the ota operation to fix the ash warnings about `change_attribute` after validation Signed-off-by: Francesco Noacco <[email protected]>
…vpkkqvx chore: update ash
Port changes occurred in the release-0.9 branch into the main branch.
…rd-port-release-0.9-into-main
Ota operations expose an optional `UpdateTarget`. It is a reference to the update target that created the managed ota operation Closes edgehog-device-manager#356 Signed-off-by: Luca Zaninotto <[email protected]>
…operation_update_campaign feat(ota): exposing optional update target of OTA
closes edgehog-device-manager#431 . Adds `one_realm_per_tenant` identity on realms Signed-off-by: Luca Zaninotto <[email protected]>
previously, calling Ash.destroy! on a base image would crash the program because Edgehog.BaseImages.Uploaders.BaseImage.filename/2 would try to access the field `base_image_version` of a BaseImage, which does not exist Signed-off-by: Francesco Noacco <[email protected]>
…xmlmoou fix(bucket_storage): image deletion
- Reconciling tenant is done directly in seeds when it gets created - Edgehog in 5 minutes does no longer instruct users to manually reconcile the tenant with astarte Signed-off-by: Luca Zaninotto <[email protected]>
chore(seeds): reconcile tenant when seeding
Signed-off-by: Francesco Noacco <[email protected]>
…wmlpnuz forward port 'release-0.9' into main
add runtime s3 configuration for the test environment as well as prod. this is needed during CI but should not affect normal use Signed-off-by: Francesco Noacco <[email protected]>
Signed-off-by: Simone Orru <[email protected]>
Signed-off-by: Simone Orru <[email protected]>
Replace the old Edgehog logo with the Clea logo in the documentation. Signed-off-by: Omar <[email protected]>
- Add favicon to the Edgehog - Replace old Edgehog logo branding with the new Clea Edgehog branding Signed-off-by: Omar <[email protected]>
…ge-devices Fix doc page devices
…te_branding Update branding
Port changes occurred in the release-0.9 branch into the main branch.
…rd-port-release-0.9-into-main
add azure support by adding a waffle compatible storage module based on azurex. new environment variables were added for configuration: - STORAGE_TYPE, which can be either s3 or azure - AZURE_BLOB_ENDPOINT: equivalent to s3's asset_host. maps to azurex's api_url. - AZURE_REGION: the region for the blob storage. only used if AZURE_BLOB_ENDPOINT is unset. - AZURE_CONTAINER: equivalent to s3's bucket - AZURE_STORAGE_ACCOUNT_NAME: azure's AccountName - AZURE_STORAGE_ACCOUNT_KEY: azure's AccountKey - AZURE_CONNECTION_STRING: an azure connection string. maps to previous values. Signed-off-by: Francesco Noacco <[email protected]>
feat: azure support
- Ensured `pageIndex` remains valid when `data.length` or `maxPageRows` change - Added logic to adjust `pageIndex` only when it exceeds the new total page count - Prevented unnecessary resets to the first page when updates occur, allowing users to stay on their current page if it remains valid whenever possible. Signed-off-by: Omar <[email protected]>
…table_refresh Preserve valid Table pageIndex on data update
Adds ssl/tls support for the edgehog <-> database communication. Closes edgehog-device-manager#419. Signed-off-by: Luca Zaninotto <[email protected]>
chore(database): Add ssl support
- updating `ash`: 3.4.44 -> 3.4.52 - updating `ash_postgres` 2.4.15 -> 2.4.21 - updating `ash_graphql` 1.4.4 -> 1.4.7 - defers the load of the `realm_management_client` when reconciling all - tenants. Previously we could ignore the tenant when loading because of - a bug (see [ash changelog](https://github.com/ash-project/ash/blob/main/CHANGELOG.md#v3445-2024-12-10)) Signed-off-by: Luca Zaninotto <[email protected]>
…-update chore(ash): update ash
Closes edgehog-device-manager#504. Manages resource cleanup on tenant deletion, deleting base images, ephemeral images and system models images on remote storage. Signed-off-by: Luca Zaninotto <[email protected]>
Adds a template that can be used with the `reuse` tool: Files can be
updated automatically with:
```sh
reuse annotate <file> \
--copyright 'SECO Mind Srl' \
--copyright-prefix string \
--merge-copyrights \
--template apache
```
Signed-off-by: Luca Zaninotto <[email protected]>
…se-template chore(reuse): apache license template
When creating and updating an update channel, target group ids are validated to be available, meaning: - they are present in the DB - they are not related to any other update channel closes edgehog-device-manager#529 Signed-off-by: Luca Zaninotto <[email protected]>
…ors-update-channel chore(update_channel): better errors
…ant-cleanup chore(tenants): tenant cleanup
Update channels can have zero target device groups. Closes edgehog-device-manager#399 and Closes edgehog-device-manager#518. Signed-off-by: Luca Zaninotto <[email protected]>
…w-empty-target feat(update_channel) allow update channels to have 0 update groups
Signed-off-by: Davide Briani <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.