diff --git a/.3rd-party/README.md b/.3rd-party/README.md
index efce1189c..35c2be1eb 100644
--- a/.3rd-party/README.md
+++ b/.3rd-party/README.md
@@ -1,5 +1,9 @@
# Third-Party Dependencies
-This folder provides listings of all 3rd-party dependencies incl. their licenses. There is a dedicated subfolder for each release (and milestone) holding the release-specific information.
+This folder provides listings of all 3rd-party dependencies incl. their licenses. There is a dedicated subfolder for
+each release (and milestone) holding the release-specific information.
-The files are generated using the [check-dependencies.sh](https://github.com/eclipse-hawkbit/hawkbit/tree/master/check-dependencies.sh) script. The script makes use of the [Eclipse Dash License Tool](https://github.com/eclipse/dash-licenses) which identifies and vets the licenses of the project content.
+The files are generated using
+the [check-dependencies.sh](https://github.com/eclipse-hawkbit/hawkbit/tree/master/check-dependencies.sh) script. The
+script makes use of the [Eclipse Dash License Tool](https://github.com/eclipse/dash-licenses) which identifies and vets
+the licenses of the project content.
diff --git a/.github/workflows/first-interaction.yml b/.github/workflows/first-interaction.yml
index de2b244f2..9374f148a 100644
--- a/.github/workflows/first-interaction.yml
+++ b/.github/workflows/first-interaction.yml
@@ -2,7 +2,7 @@ name: First User Interaction
on:
pull_request_target:
- types: [opened]
+ types: [ opened ]
jobs:
greeting:
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 9ccb7b219..0450adaa6 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -2,7 +2,10 @@
## Our Pledge
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
+participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
+disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
## Our Standards
@@ -24,23 +27,35 @@ Examples of unacceptable behavior by participants include:
## Our Responsibilities
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
+appropriate and fair corrective action in response to any instances of unacceptable behavior.
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
+project or its community. Examples of representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed representative at an online or offline
+event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hawkbit-dev@eclipse.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
+hawkbit-dev@eclipse.org. The project team will review and investigate all complaints, and will respond in a way that it
+deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the
+reporter of an incident. Further details of specific enforcement policies may be posted separately.
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
+repercussions as determined by other members of the project's leadership.
## Attribution
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available
+at [http://contributor-covenant.org/version/1/4][version]
[homepage]: http://contributor-covenant.org
+
[version]: http://contributor-covenant.org/version/1/4/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3834bd2cb..72b5a6380 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,37 +9,44 @@ Please read this if you intend to contribute to the project.
### Code Style
* Java files:
- * we follow the standard eclipse IDE (built in) code formatter with the following changes:
- * Tab policy: spaces only: 4
- * We recommend using at least Eclipse [Mars](https://www.eclipse.org/mars/) IDE release. It seems that the Java code formatter line break handling has been changed between [Luna](https://www.eclipse.org/luna/) and Mars.
+ * we follow the standard eclipse IDE (built in) code formatter with the following changes:
+ * Tab policy: spaces only: 4
+ * We recommend using at least Eclipse [Mars](https://www.eclipse.org/mars/) IDE release. It seems that the Java code
+ formatter line break handling has been changed between [Luna](https://www.eclipse.org/luna/) and Mars.
* XML files:
- * we follow the standard eclipse IDE XML formatter with the following changes:
- * Indent using spaces only: 3
+ * we follow the standard eclipse IDE XML formatter with the following changes:
+ * Indent using spaces only: 3
* SCSS files:
- * we follow the standard [scss-lint](https://github.com/brigade/scss-lint/) rules with the following exception:
- * disabled rules: ImportantRule, PropertySortOrder
+ * we follow the standard [scss-lint](https://github.com/brigade/scss-lint/) rules with the following exception:
+ * disabled rules: ImportantRule, PropertySortOrder
* Sonarqube:
- * Our rule set can be found [here](https://sonarcloud.io/organizations/bosch-iot-rollouts/rules)
- * Sonarqube reports can be found [here](https://sonarcloud.io/project/overview?id=org.eclipse.hawkbit%3Ahawkbit-parent)
+ * Our rule set can be found [here](https://sonarcloud.io/organizations/bosch-iot-rollouts/rules)
+ * Sonarqube reports can be
+ found [here](https://sonarcloud.io/project/overview?id=org.eclipse.hawkbit%3Ahawkbit-parent)
### Utility library usage
-hawkBit has currently [Apache commons lang](https://commons.apache.org/proper/commons-lang/) on the classpath in several of its modules. However, we see introducing too many utility libraries problematic as we force these as transitive dependencies on hawkBit users. We in fact are looking into reducing them in future not adding new ones.
+hawkBit has currently [Apache commons lang](https://commons.apache.org/proper/commons-lang/) on the classpath in several
+of its modules. However, we see introducing too many utility libraries problematic as we force these as transitive
+dependencies on hawkBit users. We in fact are looking into reducing them in future not adding new ones.
So we kindly ask contributors:
* not introduce extra utility library dependencies
-* keep them out of the core modules (e.g. hawkbit-core, hawkbit-rest-core, hawkbit-http-security) to avoid that all modules have them as transitive dependency
+* keep them out of the core modules (e.g. hawkbit-core, hawkbit-rest-core, hawkbit-http-security) to avoid that all
+ modules have them as transitive dependency
* use utility functions in general based in the following priority:
- * use utility functions from JDK if feasible
- * use Spring utility classes if feasible
- * use [Apache commons lang](https://commons.apache.org/proper/commons-lang/) if feasible
+ * use utility functions from JDK if feasible
+ * use Spring utility classes if feasible
+ * use [Apache commons lang](https://commons.apache.org/proper/commons-lang/) if feasible
### Test documentation
-Please document the test cases that you contribute by means of [Allure](https://docs.qameta.io/allure/) annotations and proper test method naming.
+Please document the test cases that you contribute by means of [Allure](https://docs.qameta.io/allure/) annotations and
+proper test method naming.
-All test classes are documented with [Allure's](https://docs.qameta.io/allure/#_behaviours_mapping) **@Feature** and **@Story** annotations in the following format:
+All test classes are documented with [Allure's](https://docs.qameta.io/allure/#_behaviours_mapping) **@Feature** and *
+*@Story** annotations in the following format:
```java
@Feature("TEST_TYPE - HAWKBIT_COMPONENT")
@@ -49,7 +56,8 @@ All test classes are documented with [Allure's](https://docs.qameta.io/allure/#_
Test types are:
* Unit Tests - for single units tests with a mocked environment
-* Component Tests - for complete components including lower layers, e.g. Spring MVC test on rest API including repository and database.
+* Component Tests - for complete components including lower layers, e.g. Spring MVC test on rest API including
+ repository and database.
* Integration Tests - including clients, e.g. Selenium UI tests with various browsers.
* System Tests - on target environments, e.g. Cloud Foundry.
@@ -66,7 +74,8 @@ Examples for hawkBit components:
@Story("Distribution Set Type Resource")
```
-In addition all test method's name describes in **camel case** what the test is all about and has in addition a long description in Allures **@Description** annotation.
+In addition all test method's name describes in **camel case** what the test is all about and has in addition a long
+description in Allures **@Description** annotation.
## Legal considerations for your contribution
@@ -129,8 +138,11 @@ Submit a pull request via the normal GitHub UI (desktop or web).
## Reporting a security vulnerability
-If you find a vulnerability, **DO NOT** disclose it in the public immediately! Instead, give us the possibility to fix it beforehand.
-So please don’t report your finding using GitHub issues and better head over to [https://eclipse.org/security](https://eclipse.org/security) and learn how to disclose a vulnerability in a safe and responsible manner
+If you find a vulnerability, **DO NOT** disclose it in the public immediately! Instead, give us the possibility to fix
+it beforehand.
+So please don’t report your finding using GitHub issues and better head over
+to [https://eclipse.org/security](https://eclipse.org/security) and learn how to disclose a vulnerability in a safe and
+responsible manner
## Further information
diff --git a/MIGRATION.md b/MIGRATION.md
index 40bb6a1a9..e24922a61 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -13,13 +13,17 @@
### REST API model changes for clients
-- ENTITYPagedList classes have been removed; generic `PagedList` used instead (e.g. `PagedList` instead of `TargetPagedList`).
-- ENTITYsrest classes have been removed; `List` used instead (e.g. `List` instead of `TargetsRest`)
+- ENTITYPagedList classes have been removed; generic `PagedList` used instead (e.g. `PagedList` instead
+ of `TargetPagedList`).
+- ENTITYsrest classes have been removed; `List` used instead (e.g. `List` instead
+ of `TargetsRest`)
### Renamed api annotations
-- Annotation `org.eclipse.hawkbit.rest.resource.EnableRestResources` has changed to `org.eclipse.hawkbit.mgmt.annotation.EnableMgmtApi`
-- Annotation `org.eclipse.hawkbit.ddi.resource.EnableDirectDeviceApi` has changed to `org.eclipse.hawkbit.ddi.annotation.EnableDdiApi`
+- Annotation `org.eclipse.hawkbit.rest.resource.EnableRestResources` has changed
+ to `org.eclipse.hawkbit.mgmt.annotation.EnableMgmtApi`
+- Annotation `org.eclipse.hawkbit.ddi.resource.EnableDirectDeviceApi` has changed
+ to `org.eclipse.hawkbit.ddi.annotation.EnableDdiApi`
### Renamed maven modules
@@ -29,17 +33,21 @@
### Configuration Property changes
-- `hawkbit.server.security.dos.maxTargetsPerManualAssignment` has changed to `hawkbit.server.security.dos.maxTargetDistributionSetAssignmentsPerManualAssignment`
+- `hawkbit.server.security.dos.maxTargetsPerManualAssignment` has changed
+ to `hawkbit.server.security.dos.maxTargetDistributionSetAssignmentsPerManualAssignment`
## Milestone 0.3.0M7
### Configuration Property changes
-- Due to Spring Boot version upgrade (see [spring boot 2.2 deprecations](https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes#deprecations-in-spring-boot-22)) `server.use-forward-headers` has changed to `server.forward-headers-strategy`
+- Due to Spring Boot version upgrade (
+ see [spring boot 2.2 deprecations](https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes#deprecations-in-spring-boot-22)) `server.use-forward-headers`
+ has changed to `server.forward-headers-strategy`
## Upgrade from Master Branch (after 0.3.0M6) to 0.3.0M7
-Due to changes in the DB migration scripts within PR [#1017](https://github.com/eclipse-hawkbit/hawkbit/pull/1017) the Hawkbit will not start up if one of the following cases is true:
+Due to changes in the DB migration scripts within PR [#1017](https://github.com/eclipse-hawkbit/hawkbit/pull/1017) the
+Hawkbit will not start up if one of the following cases is true:
- DB2 database is used
- MSSQL database is used and the `sp_action` table is not empty
@@ -47,9 +55,13 @@ Due to changes in the DB migration scripts within PR [#1017](https://github.com/
The script was fixed with PR [#1061](https://github.com/eclipse-hawkbit/hawkbit/pull/1061).
-In case you upgrade from 0.3.0M6 to 0.3.0M7 there is no issue. But if you have built the Hawkbit from the master branch between PR [#1017](https://github.com/eclipse-hawkbit/hawkbit/pull/1017) and PR [#1061](https://github.com/eclipse-hawkbit/hawkbit/pull/1061), use PostgreSQL or MSSQL and upgrade to 0.3.0M7, it will fail at startup with the message: `Validate failed: Migration checksum mismatch for migration version 1.12.16`
+In case you upgrade from 0.3.0M6 to 0.3.0M7 there is no issue. But if you have built the Hawkbit from the master branch
+between PR [#1017](https://github.com/eclipse-hawkbit/hawkbit/pull/1017) and
+PR [#1061](https://github.com/eclipse-hawkbit/hawkbit/pull/1061), use PostgreSQL or MSSQL and upgrade to 0.3.0M7, it
+will fail at startup with the message: `Validate failed: Migration checksum mismatch for migration version 1.12.16`
-This can be fixed by adapting the schema_version table of the database. The checksum field of the entry with the version 1.12.16 has to be changed (mind the minus):
+This can be fixed by adapting the schema_version table of the database. The checksum field of the entry with the version
+1.12.16 has to be changed (mind the minus):
- -1684307461 for MSSQL
- -596342656 for PostgreSql
diff --git a/README.md b/README.md
index b61041df6..83fd6b798 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,9 @@
# Eclipse hawkBit™ - Update Server
-Eclipse [hawkBit](http://www.eclipse.org/hawkbit/index.html) is an domain independent back end solution for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.
+Eclipse [hawkBit](http://www.eclipse.org/hawkbit/index.html) is an domain independent back end solution for rolling out
+software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based
+networking infrastructure.
Build:
[](https://github.com/eclipse-hawkbit/hawkbit/actions/workflows/verify.yml)
@@ -13,8 +15,8 @@ Build:
License:
[](https://opensource.org/licenses/EPL-2.0)
-Docker:
-[](https://hub.docker.com/r/hawkbit/hawkbit-update-server)
+Docker:
+[](https://hub.docker.com/r/hawkbit/hawkbit-update-server)
[](https://hub.docker.com/r/hawkbit/hawkbit-update-server)
[](https://hub.docker.com/search?q=hawkbit%2Fhawkbit-update-server&type=image)
@@ -25,13 +27,17 @@ see [hawkBit Documentation](https://www.eclipse.dev/hawkbit/)
# Contact us
- Having questions about hawkBit? Check [Stack Overflow](https://stackoverflow.com/questions/tagged/eclipse-hawkbit)
-- Want to chat with the team behind hawkBit? [](https://gitter.im/eclipse/hawkbit?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+- Want to chat with the team behind
+ hawkBit? [](https://gitter.im/eclipse/hawkbit?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
- Having issues with hawkBit? Open a [GitHub issue](https://github.com/eclipse-hawkbit/hawkbit/issues).
- You can also check out our [Project Homepage](https://www.eclipse.dev/hawkbit) for further contact options.
# hawkBit sandbox
-We offer a sandbox installation that is free for everyone to try out hawkBit. However, keep in mind that the sandbox database will be reset from time to time. It is also not possible to upload any artifacts into the sandbox. But you can use it to try out the Management API and DDI API. Keep in mind as well that you are not permitted to store any kind of personal data in the sandbox.
+We offer a sandbox installation that is free for everyone to try out hawkBit. However, keep in mind that the sandbox
+database will be reset from time to time. It is also not possible to upload any artifacts into the sandbox. But you can
+use it to try out the Management API and DDI API. Keep in mind as well that you are not permitted to store any kind of
+personal data in the sandbox.
[https://hawkbit.eclipseprojects.io](https://hawkbit.eclipseprojects.io)
@@ -42,29 +48,44 @@ In addition the following vendors offer free trial accounts for their hawkBit co
# Device Integration (Client libraries)
-hawkBit exposes HTTP/JSON based [Direct Device Integration (API) API](https://www.eclipse.org/hawkbit/apis/ddi_api/) that allow any update client to integrate quite easily.
+hawkBit exposes HTTP/JSON based [Direct Device Integration (API) API](https://www.eclipse.org/hawkbit/apis/ddi_api/)
+that allow any update client to integrate quite easily.
-The [Eclipse Hara subproject](https://projects.eclipse.org/projects/iot.hawkbit.hara) aims to provide a reference agent software implementation of the Eclipse hawkBit device API. The [hara-ddiclient repository](https://github.com/eclipse-hara/hara-ddiclient) provides:
+The [Eclipse Hara subproject](https://projects.eclipse.org/projects/iot.hawkbit.hara) aims to provide a reference agent
+software implementation of the Eclipse hawkBit device API.
+The [hara-ddiclient repository](https://github.com/eclipse-hara/hara-ddiclient) provides:
- a Kotlin library that facilitates and speeds up the development of DDI API clients running on the JVM
- a virtual-device application which provides:
- a reference example on how to use the library
- a configurable virtual device that can be used for different testing scenarios
-The hara-ddiclient library has [reached version 2.x](https://github.com/eclipse-hara/hara-ddiclient/releases), and has been successfully used in production for years.
+The hara-ddiclient library has [reached version 2.x](https://github.com/eclipse-hara/hara-ddiclient/releases), and has
+been successfully used in production for years.
-Additionally, the hawkBit project has the long term goal to provide [Eclipse Hono](https://github.com/eclipse/hono) integration which will provide connectivity through various IoT protocols and as a result will allow a wide range of clients to connect to hawkBit.
+Additionally, the hawkBit project has the long term goal to provide [Eclipse Hono](https://github.com/eclipse/hono)
+integration which will provide connectivity through various IoT protocols and as a result will allow a wide range of
+clients to connect to hawkBit.
## Other open-source hawkBit Clients
There are clients outside of the Eclipse IoT eco system as well, e.g.:
-- [SWupdate](https://github.com/sbabic/swupdate) which is a Linux Update agent with focus on a efficient and safe way to update embedded systems.
-- [rauc-hawkbit-updater](https://github.com/rauc/rauc-hawkbit-updater) which is a hawkBit client for the [RAUC](https://github.com/rauc/rauc) update framework written in C/glib.
-- [rauc-hawkbit](https://github.com/rauc/rauc-hawkbit) which is a python-based hawkBit client demo application and library for the [RAUC](https://github.com/rauc/rauc) update framework.
-- [hawkbit-rs](https://github.com/collabora/hawkbit-rs) provides a couple of [Rust](https://www.rust-lang.org) crates to help [implement](https://crates.io/crates/hawkbit) and [test](https://crates.io/crates/hawkbit_mock) hawkBit clients.
-- [Zephyr-RTOS](https://docs.zephyrproject.org/apidoc/latest/group__hawkbit.html#details): The Zephyr OS is a small-footprint kernel designed for use on resource-constrained and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated embedded controllers, smart watches, and IoT wireless applications.
-- [ChirpStack](https://www.chirpstack.io/docs/chirpstack-gateway-os/use/software-update.html): ChirpStack Gateway OS uses [SWUpdate](https://github.com/sbabic/swupdate) for handling updates which can be integrated with Eclipse hawkBit. ChirpStack is an open-source LoRaWAN Network Server which can be used to to setup private or public LoRaWAN networks.
+- [SWupdate](https://github.com/sbabic/swupdate) which is a Linux Update agent with focus on a efficient and safe way to
+ update embedded systems.
+- [rauc-hawkbit-updater](https://github.com/rauc/rauc-hawkbit-updater) which is a hawkBit client for
+ the [RAUC](https://github.com/rauc/rauc) update framework written in C/glib.
+- [rauc-hawkbit](https://github.com/rauc/rauc-hawkbit) which is a python-based hawkBit client demo application and
+ library for the [RAUC](https://github.com/rauc/rauc) update framework.
+- [hawkbit-rs](https://github.com/collabora/hawkbit-rs) provides a couple of [Rust](https://www.rust-lang.org) crates to
+ help [implement](https://crates.io/crates/hawkbit) and [test](https://crates.io/crates/hawkbit_mock) hawkBit clients.
+- [Zephyr-RTOS](https://docs.zephyrproject.org/apidoc/latest/group__hawkbit.html#details): The Zephyr OS is a
+ small-footprint kernel designed for use on resource-constrained and embedded systems: from simple embedded
+ environmental sensors and LED wearables to sophisticated embedded controllers, smart watches, and IoT wireless
+ applications.
+- [ChirpStack](https://www.chirpstack.io/docs/chirpstack-gateway-os/use/software-update.html): ChirpStack Gateway OS
+ uses [SWUpdate](https://github.com/sbabic/swupdate) for handling updates which can be integrated with Eclipse hawkBit.
+ ChirpStack is an open-source LoRaWAN Network Server which can be used to to setup private or public LoRaWAN networks.
# Runtime dependencies and support
@@ -72,20 +93,22 @@ There are clients outside of the Eclipse IoT eco system as well, e.g.:
## SQL database
-| Database | H2 | MySQL/MariaDB | MS SQL Server | PostgreSQL | IBM DB2 |
-| --------------------------------- | :----------------------------------------------------: | :-------------------------------------------------------------------------: | :--------------------------------------------------------------: | :----------------------------------------------------------------: | :----------------: |
-| DDLs maintained by project | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Test dependencies defined | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | |
-| Versions tested | 2.1 | MySQL 8.0.23, AWS Aurora | MS SQL Server 2017/2019 | PostgreSQL 12/13 | DB2 Server v11.1 |
-| Docker image with driver provided | :white_check_mark: | :white_check_mark: (Tag: "-mysql") | :white_check_mark: | :white_check_mark: | |
+| Database | H2 | MySQL/MariaDB | MS SQL Server | PostgreSQL | IBM DB2 |
+|-----------------------------------|:------------------------------------------------------:|:---------------------------------------------------------------------------:|:-----------------------------------------------------------------:|:-----------------------------------------------------------------:|:------------------:|
+| DDLs maintained by project | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| Test dependencies defined | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | |
+| Versions tested | 2.1 | MySQL 8.0.23, AWS Aurora | MS SQL Server 2017/2019 | PostgreSQL 12/13 | DB2 Server v11.1 |
+| Docker image with driver provided | :white_check_mark: | :white_check_mark: (Tag: "-mysql") | :white_check_mark: | :white_check_mark: | |
| JDBC driver | [H2 2.1.214](https://github.com/h2database/h2database) | [MariaDB Connector/J 2.7.8](https://github.com/MariaDB/mariadb-connector-j) | [MSSQL-JDBC 10.2.3.jre8](https://github.com/Microsoft/mssql-jdbc) | [PostgreSQL JDBC Driver 42.3.8](https://github.com/pgjdbc/pgjdbc) | |
-| Status | Test, Dev | Production grade | Production grade | Test, Dev | Test, Dev |
+| Status | Test, Dev | Production grade | Production grade | Test, Dev | Test, Dev |
## (Optional) RabbitMQ: 3.6,3.7,3.8
# Getting Started
-We are providing a [Spring Boot](https://projects.spring.io/spring-boot/) based reference [Update Server](hawkbit-runtime/hawkbit-update-server) including embedded H2 DB for test and evaluation purposes.
+We are providing a [Spring Boot](https://projects.spring.io/spring-boot/) based
+reference [Update Server](hawkbit-runtime/hawkbit-update-server) including embedded H2 DB for test and evaluation
+purposes.
Run with docker:
```bash
@@ -96,13 +119,18 @@ Open the update server in your browser:
[localhost:8080](http://localhost:8080)
-See below for how to build and run the update server on your own. In addition we have a [guide](https://www.eclipse.org/hawkbit/guides/runhawkbit/) for setting up a complete landscape.
+See below for how to build and run the update server on your own. In addition we have
+a [guide](https://www.eclipse.org/hawkbit/guides/runhawkbit/) for setting up a complete landscape.
-**Note**: this docker image supports both DDI and DMF APIs. However, in order to have DMF API working you shall have started additionally RabbitMQ on localhost:5672 with user guest/guest. Then the DMF will use / vhost. See more at [guide](https://www.eclipse.org/hawkbit/guides/runhawkbit/) -> _Configure RabbitMQ connection settings_.
+**Note**: this docker image supports both DDI and DMF APIs. However, in order to have DMF API working you shall have
+started additionally RabbitMQ on localhost:5672 with user guest/guest. Then the DMF will use / vhost. See more
+at [guide](https://www.eclipse.org/hawkbit/guides/runhawkbit/) -> _Configure RabbitMQ connection settings_.
# hawkBit (Spring boot) starters
-Next to the [Update Server](hawkbit-runtime/hawkbit-update-server) we are also providing a set of [Spring Boot Starters](hawkbit-starters) to quick start your own [Spring Boot](https://projects.spring.io/spring-boot/) based application.
+Next to the [Update Server](hawkbit-runtime/hawkbit-update-server) we are also providing a set
+of [Spring Boot Starters](hawkbit-starters) to quick start your
+own [Spring Boot](https://projects.spring.io/spring-boot/) based application.
# Clone, build and run hawkBit
@@ -135,8 +163,16 @@ java -jar ./hawkbit-example-mgmt-simulator/target/hawkbit-example-mgmt-simulator
# Status and API stability
-hawkBit is currently in '0.X' semantic version. That is due to the need that there is still content in hawkBit that is in need for refactoring. That includes the maven module structure, Spring Boot Properties, Spring Boot auto configuration as well as internal Java APIs (e.g. the [repository API](https://github.com/eclipse-hawkbit/hawkbit/issues/197) ).
+hawkBit is currently in '0.X' semantic version. That is due to the need that there is still content in hawkBit that is
+in need for refactoring. That includes the maven module structure, Spring Boot Properties, Spring Boot auto
+configuration as well as internal Java APIs (e.g.
+the [repository API](https://github.com/eclipse-hawkbit/hawkbit/issues/197) ).
-However, the device facing [DDI API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-rest/hawkbit-ddi-api) is on major version 'v1' and will be kept stable.
+However, the device
+facing [DDI API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-rest/hawkbit-ddi-api) is on major
+version 'v1' and will be kept stable.
-Server facing and [DMF API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api) are [Management API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-rest/hawkbit-mgmt-api) are on v1 as well. However, we cannot fully guarantee the same stability during hawkBit's 0.X development but we will try as best we can.
+Server facing and [DMF API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api)
+are [Management API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-rest/hawkbit-mgmt-api) are on v1 as
+well. However, we cannot fully guarantee the same stability during hawkBit's 0.X development but we will try as best we
+can.
diff --git a/SECURITY.md b/SECURITY.md
index e0432d2c2..16785b7f4 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -1,4 +1,7 @@
# Reporting a Security Vulnerability
-If you find a vulnerability, **DO NOT** disclose it in the public immediately! Instead, give us the possibility to fix it beforehand.
-So please don’t report your finding using GitHub issues and better head over to [https://eclipse.org/security](https://eclipse.org/security) and learn how to disclose a vulnerability in a safe and responsible manner
+If you find a vulnerability, **DO NOT** disclose it in the public immediately! Instead, give us the possibility to fix
+it beforehand.
+So please don’t report your finding using GitHub issues and better head over
+to [https://eclipse.org/security](https://eclipse.org/security) and learn how to disclose a vulnerability in a safe and
+responsible manner
diff --git a/eclipse_codeformatter.xml b/eclipse_codeformatter.xml
index 2b2b4a809..f087b31eb 100644
--- a/eclipse_codeformatter.xml
+++ b/eclipse_codeformatter.xml
@@ -1,380 +1,504 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/hawkbit-repository/README.md b/hawkbit-repository/README.md
index 2ee2fea11..72ff30628 100644
--- a/hawkbit-repository/README.md
+++ b/hawkbit-repository/README.md
@@ -25,7 +25,8 @@ When starting a rollout, for all targets within this rollout deployment actions
of the first group will be started immediately all other deployment actions will be scheduled.
> Due rollouts might include a large number of targets and deployment group, creation as well as starting a rollout
-> might take some time and therefore the creation and starting of an rollout is executed asynchronously. The creation and
+> might take some time and therefore the creation and starting of an rollout is executed asynchronously. The creation
+> and
> starting progress is reflected by the rollout's status attribute
### Rollout Creation
diff --git a/hawkbit-repository/hawkbit-repository-api/src/main/java/org/eclipse/hawkbit/repository/event/remote/entity/AbstractRolloutGroupEvent.java b/hawkbit-repository/hawkbit-repository-api/src/main/java/org/eclipse/hawkbit/repository/event/remote/entity/AbstractRolloutGroupEvent.java
index 95decb151..4c06e5683 100644
--- a/hawkbit-repository/hawkbit-repository-api/src/main/java/org/eclipse/hawkbit/repository/event/remote/entity/AbstractRolloutGroupEvent.java
+++ b/hawkbit-repository/hawkbit-repository-api/src/main/java/org/eclipse/hawkbit/repository/event/remote/entity/AbstractRolloutGroupEvent.java
@@ -41,6 +41,11 @@ public abstract class AbstractRolloutGroupEvent extends RemoteEntityEvent
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-sdk
- ${revision}
-
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0">
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-sdk
+ ${revision}
+
- hawkbit-sdk-commons
- hawkBit :: SDK :: Commons
- SDK commons
+ hawkbit-sdk-commons
+ hawkBit :: SDK :: Commons
+ SDK commons
-
-
-
- org.springframework.cloud
- spring-cloud-starter-openfeign
- ${spring-cloud-starter-openfeign.version}
-
-
- io.github.openfeign
- feign-hc5
- ${openfeign-hc5.version}
-
-
- org.springframework.boot
- spring-boot-starter-hateoas
-
-
+
+
+ org.springframework.cloud
+ spring-cloud-starter-openfeign
+ ${spring-cloud-starter-openfeign.version}
+
+
+ io.github.openfeign
+ feign-hc5
+ ${openfeign-hc5.version}
+
+
+ org.springframework.boot
+ spring-boot-starter-hateoas
+
+
diff --git a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/Controller.java b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/Controller.java
index c52b3e6c7..d63ef2095 100644
--- a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/Controller.java
+++ b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/Controller.java
@@ -11,8 +11,6 @@ package org.eclipse.hawkbit.sdk;
import lombok.Builder;
import lombok.Data;
-import lombok.ToString;
-import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.lang.NonNull;
import org.springframework.lang.Nullable;
diff --git a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitClient.java b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitClient.java
index 5dbf54f86..d170277de 100644
--- a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitClient.java
+++ b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitClient.java
@@ -9,6 +9,11 @@
*/
package org.eclipse.hawkbit.sdk;
+import java.nio.charset.StandardCharsets;
+import java.util.Base64;
+import java.util.Objects;
+import java.util.function.BiFunction;
+
import feign.Client;
import feign.Contract;
import feign.Feign;
@@ -20,49 +25,42 @@ import lombok.Builder;
import lombok.extern.slf4j.Slf4j;
import org.springframework.util.ObjectUtils;
-import java.nio.charset.StandardCharsets;
-import java.util.Base64;
-import java.util.Objects;
-import java.util.function.BiFunction;
-
@Slf4j
@Builder
public class HawkbitClient {
private static final String AUTHORIZATION = "Authorization";
- private static final ErrorDecoder DEFAULT_ERROR_DECODER_0 = new ErrorDecoder.Default();
+ public static final BiFunction DEFAULT_REQUEST_INTERCEPTOR_FN =
+ (tenant, controller) ->
+ controller == null ?
+ template -> {
+ template.header(
+ AUTHORIZATION,
+ "Basic " +
+ Base64.getEncoder()
+ .encodeToString(
+ (Objects.requireNonNull(tenant.getUsername(), "User is null!") +
+ ":" +
+ Objects.requireNonNull(tenant.getPassword(),
+ "Password is not available!"))
+ .getBytes(StandardCharsets.ISO_8859_1)));
+ } :
+ template -> {
+ if (ObjectUtils.isEmpty(tenant.getGatewayToken())) {
+ if (!ObjectUtils.isEmpty(controller.getSecurityToken())) {
+ template.header(AUTHORIZATION, "TargetToken " + controller.getSecurityToken());
+ } // else do not sent authentication
+ } else {
+ template.header(AUTHORIZATION, "GatewayToken " + tenant.getGatewayToken());
+ }
+ };
+ private static final ErrorDecoder DEFAULT_ERROR_DECODER_0 = new ErrorDecoder.Default();
public static final ErrorDecoder DEFAULT_ERROR_DECODER = (methodKey, response) -> {
final Exception e = DEFAULT_ERROR_DECODER_0.decode(methodKey, response);
log.trace("REST API call failed!", e);
return e;
};
-
- public static final BiFunction DEFAULT_REQUEST_INTERCEPTOR_FN =
- (tenant, controller) ->
- controller == null ?
- template -> {
- template.header(
- AUTHORIZATION,
-
- "Basic " +
- Base64.getEncoder()
- .encodeToString(
- (Objects.requireNonNull(tenant.getUsername(), "User is null!") +
- ":" +
- Objects.requireNonNull(tenant.getPassword(),"Password is not available!"))
- .getBytes(StandardCharsets.ISO_8859_1)));
- } :
- template -> {
- if (ObjectUtils.isEmpty(tenant.getGatewayToken())) {
- if (!ObjectUtils.isEmpty(controller.getSecurityToken())) {
- template.header(AUTHORIZATION, "TargetToken " + controller.getSecurityToken());
- } // else do not sent authentication
- } else {
- template.header(AUTHORIZATION, "GatewayToken " + tenant.getGatewayToken());
- }
- };
-
private final HawkbitServer hawkBitServerProperties;
private final Client client;
@@ -100,6 +98,7 @@ public class HawkbitClient {
public T mgmtService(final Class serviceType, final Tenant tenantProperties) {
return service(serviceType, tenantProperties, null);
}
+
public T ddiService(final Class serviceType, final Tenant tenantProperties, final Controller controller) {
return service(serviceType, tenantProperties, controller);
}
@@ -113,7 +112,7 @@ public class HawkbitClient {
.requestInterceptor(requestInterceptorFn.apply(tenant, controller))
.target(serviceType,
controller == null ?
- hawkBitServerProperties.getMgmtUrl() :
- hawkBitServerProperties.getDdiUrl());
+ hawkBitServerProperties.getMgmtUrl() :
+ hawkBitServerProperties.getDdiUrl());
}
}
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitSDKConfigurtion.java b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitSDKConfigurtion.java
index f187036a3..fb17b6297 100644
--- a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitSDKConfigurtion.java
+++ b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitSDKConfigurtion.java
@@ -9,6 +9,10 @@
*/
package org.eclipse.hawkbit.sdk;
+import java.lang.annotation.Annotation;
+import java.lang.reflect.Method;
+import java.util.LinkedHashMap;
+
import feign.Contract;
import feign.MethodMetadata;
import feign.RequestInterceptor;
@@ -30,13 +34,9 @@ import org.springframework.hateoas.config.EnableHypermediaSupport;
import org.springframework.hateoas.config.WebConverters;
import org.springframework.http.MediaType;
-import java.lang.annotation.Annotation;
-import java.lang.reflect.Method;
-import java.util.LinkedHashMap;
-
@Slf4j
@Configuration
-@EnableConfigurationProperties({ HawkbitServer.class, Tenant.class})
+@EnableConfigurationProperties({ HawkbitServer.class, Tenant.class })
@EnableHypermediaSupport(type = EnableHypermediaSupport.HypermediaType.HAL)
@Import(FeignClientsConfiguration.class)
@PropertySource("classpath:/hawkbit-sdk-defaults.properties")
@@ -62,7 +62,7 @@ public class HawkbitSDKConfigurtion {
@Bean
@ConditionalOnMissingBean
@ConditionalOnNotWebApplication
- @ConditionalOnClass({ WebConverters.class})
+ @ConditionalOnClass({ WebConverters.class })
public HttpMessageConverterCustomizer webConvertersCustomizerOverrider(WebConverters webConverters) {
return new WebConvertersCustomizer(webConverters);
}
diff --git a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitServer.java b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitServer.java
index 3e13d1ec7..58a98a6bc 100644
--- a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitServer.java
+++ b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/HawkbitServer.java
@@ -13,7 +13,7 @@ import lombok.Data;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.lang.NonNull;
-@ConfigurationProperties(prefix="hawkbit.server")
+@ConfigurationProperties(prefix = "hawkbit.server")
@Data
public class HawkbitServer {
diff --git a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/spi/ArtifactHandler.java b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/spi/ArtifactHandler.java
index 20f73b8f1..351ff9203 100644
--- a/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/spi/ArtifactHandler.java
+++ b/hawkbit-sdk/hawkbit-sdk-commons/src/main/java/org/eclipse/hawkbit/sdk/spi/ArtifactHandler.java
@@ -25,11 +25,8 @@ public interface ArtifactHandler {
interface DownloadHandler {
- enum Status {
- SUCCESS, ERROR
- }
-
DownloadHandler SKIP = new DownloadHandler() {
+
@Override
public void read(byte[] buff, int off, int len) {
// skip
@@ -69,5 +66,9 @@ public interface ArtifactHandler {
* @return the path to the download
*/
Optional download();
+
+ enum Status {
+ SUCCESS, ERROR
+ }
}
}
diff --git a/hawkbit-sdk/hawkbit-sdk-demo/pom.xml b/hawkbit-sdk/hawkbit-sdk-demo/pom.xml
index 3e4e8ccde..423e9f27d 100644
--- a/hawkbit-sdk/hawkbit-sdk-demo/pom.xml
+++ b/hawkbit-sdk/hawkbit-sdk-demo/pom.xml
@@ -10,72 +10,72 @@
-->
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-sdk
- ${revision}
-
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0">
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-sdk
+ ${revision}
+
- hawkbit-sdk-demo
- hawkBit :: SDK :: Test / Example
- Test / Example of how SDK could be used to for devices and for Mgmt API access
+ hawkbit-sdk-demo
+ hawkBit :: SDK :: Test / Example
+ Test / Example of how SDK could be used to for devices and for Mgmt API access
-
- 3.1.5
- org.eclipse.hawkbit.sdk.demo.multidevice.MultiDeviceApp
- ${spring.app.class}
-
+
+ 3.1.5
+ org.eclipse.hawkbit.sdk.demo.multidevice.MultiDeviceApp
+ ${spring.app.class}
+
-
-
- org.eclipse.hawkbit
- hawkbit-sdk-device
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-sdk-dmf
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-sdk-mgmt
- ${project.version}
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-sdk-device
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-sdk-dmf
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-sdk-mgmt
+ ${project.version}
+
-
- org.springframework.shell
- spring-shell-starter
- ${spring-shell.version}
-
-
+
+ org.springframework.shell
+ spring-shell-starter
+ ${spring-shell.version}
+
+
-
-
-
- org.springframework.boot
- spring-boot-maven-plugin
-
-
-
- repackage
-
-
- ${baseDir}
- JAR
-
-
-
-
-
+
+
+
+ org.springframework.boot
+ spring-boot-maven-plugin
+
+
+
+ repackage
+
+
+ ${baseDir}
+ JAR
+
+
+
+
+
-
-
- src/main/resources
-
-
-
+
+
+ src/main/resources
+
+
+
diff --git a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/device/DeviceApp.java b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/device/DeviceApp.java
index a3ac8d9c5..a04f0aa6e 100644
--- a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/device/DeviceApp.java
+++ b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/device/DeviceApp.java
@@ -9,6 +9,9 @@
*/
package org.eclipse.hawkbit.sdk.demo.device;
+import java.util.Optional;
+import java.util.concurrent.Executors;
+
import feign.Client;
import feign.Contract;
import feign.codec.Decoder;
@@ -29,9 +32,6 @@ import org.springframework.shell.standard.ShellComponent;
import org.springframework.shell.standard.ShellMethod;
import org.springframework.util.ObjectUtils;
-import java.util.Optional;
-import java.util.concurrent.Executors;
-
/**
* Abstract class representing DDI device connecting directly to hawkVit.
*/
@@ -52,7 +52,7 @@ public class DeviceApp {
@Bean
DdiTenant ddiTenant(final Tenant defaultTenant,
- final HawkbitClient hawkbitClient) {
+ final HawkbitClient hawkbitClient) {
return new DdiTenant(defaultTenant, hawkbitClient);
}
@@ -69,7 +69,6 @@ public class DeviceApp {
private final DdiController device;
private final MgmtApi mgmtApi;
-
Shell(final DdiTenant ddiTenant, final MgmtApi mgmtApi, final Optional updateHandler) {
this.ddiTenant = ddiTenant;
this.mgmtApi = mgmtApi;
@@ -88,7 +87,7 @@ public class DeviceApp {
@ShellMethod(key = "setup")
public void setup() {
mgmtApi.setupTargetAuthentication();
- mgmtApi.setupTargetToken(device.getControllerId(),device.getTargetSecurityToken());
+ mgmtApi.setupTargetToken(device.getControllerId(), device.getTargetSecurityToken());
}
@ShellMethod(key = "start")
diff --git a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/dmf/DmfApp.java b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/dmf/DmfApp.java
index 8a8e632a2..5954bbb4d 100644
--- a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/dmf/DmfApp.java
+++ b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/dmf/DmfApp.java
@@ -9,6 +9,9 @@
*/
package org.eclipse.hawkbit.sdk.demo.dmf;
+import java.util.Optional;
+import java.util.concurrent.Executors;
+
import lombok.extern.slf4j.Slf4j;
import org.eclipse.hawkbit.sdk.Controller;
import org.eclipse.hawkbit.sdk.Tenant;
@@ -26,9 +29,6 @@ import org.springframework.shell.standard.ShellComponent;
import org.springframework.shell.standard.ShellMethod;
import org.springframework.shell.standard.ShellOption;
-import java.util.Optional;
-import java.util.concurrent.Executors;
-
/**
* Abstract class representing DDI device connecting directly to hawkVit.
*/
diff --git a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/multidevice/MultiDeviceApp.java b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/multidevice/MultiDeviceApp.java
index 2ab418953..6e1c10322 100644
--- a/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/multidevice/MultiDeviceApp.java
+++ b/hawkbit-sdk/hawkbit-sdk-demo/src/main/java/org/eclipse/hawkbit/sdk/demo/multidevice/MultiDeviceApp.java
@@ -9,6 +9,9 @@
*/
package org.eclipse.hawkbit.sdk.demo.multidevice;
+import java.util.Optional;
+import java.util.concurrent.Executors;
+
import feign.Client;
import feign.Contract;
import feign.codec.Decoder;
@@ -29,9 +32,6 @@ import org.springframework.shell.standard.ShellComponent;
import org.springframework.shell.standard.ShellMethod;
import org.springframework.shell.standard.ShellOption;
-import java.util.Optional;
-import java.util.concurrent.Executors;
-
/**
* Abstract class representing DDI device connecting directly to hawkVit.
*/
@@ -52,7 +52,7 @@ public class MultiDeviceApp {
@Bean
DdiTenant ddiTenant(final Tenant defaultTenant,
- final HawkbitClient hawkbitClient) {
+ final HawkbitClient hawkbitClient) {
return new DdiTenant(defaultTenant, hawkbitClient);
}
@@ -86,7 +86,7 @@ public class MultiDeviceApp {
public void startOne(@ShellOption("--id") final String controllerId) {
final String securityTargetToken;
if (setup) {
- securityTargetToken = mgmtApi.setupTargetToken(controllerId,null);
+ securityTargetToken = mgmtApi.setupTargetToken(controllerId, null);
} else {
securityTargetToken = null;
}
@@ -96,12 +96,12 @@ public class MultiDeviceApp {
ddiTenant.getController(controllerId).ifPresentOrElse(
ddiController -> ddiController.start(Executors.newSingleThreadScheduledExecutor()),
() -> ddiTenant.createController(Controller.builder()
- .controllerId(controllerId)
- .securityToken(securityTargetToken)
- .build(),updateHandler)
+ .controllerId(controllerId)
+ .securityToken(securityTargetToken)
+ .build(), updateHandler)
.setOverridePollMillis(10_000)
.start(Executors.newSingleThreadScheduledExecutor())
- );
+ );
}
@ShellMethod(key = "stop-one")
diff --git a/hawkbit-sdk/hawkbit-sdk-device/pom.xml b/hawkbit-sdk/hawkbit-sdk-device/pom.xml
index 6b490a16b..dd69d680d 100644
--- a/hawkbit-sdk/hawkbit-sdk-device/pom.xml
+++ b/hawkbit-sdk/hawkbit-sdk-device/pom.xml
@@ -10,31 +10,31 @@
-->
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-sdk
- ${revision}
-
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0">
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-sdk
+ ${revision}
+
- hawkbit-sdk-device
- hawkBit :: SDK :: Device SDK
- Device SDK that could be used for development of devices on JVM based languages
+ hawkbit-sdk-device
+ hawkBit :: SDK :: Device SDK
+ Device SDK that could be used for development of devices on JVM based languages
-
-
- org.eclipse.hawkbit
- hawkbit-sdk-commons
- ${project.version}
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-sdk-commons
+ ${project.version}
+
-
- org.eclipse.hawkbit
- hawkbit-ddi-api
- ${project.version}
-
+
+ org.eclipse.hawkbit
+ hawkbit-ddi-api
+ ${project.version}
+
-
+
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiController.java b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiController.java
index 0aad284df..9d5453f1d 100644
--- a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiController.java
+++ b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiController.java
@@ -9,6 +9,17 @@
*/
package org.eclipse.hawkbit.sdk.device;
+import java.time.LocalTime;
+import java.time.temporal.ChronoField;
+import java.util.AbstractMap;
+import java.util.Collections;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.Optional;
+import java.util.concurrent.ScheduledExecutorService;
+import java.util.concurrent.TimeUnit;
+
import lombok.Getter;
import lombok.Setter;
import lombok.experimental.Accessors;
@@ -28,17 +39,6 @@ import org.springframework.hateoas.Link;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
-import java.time.LocalTime;
-import java.time.temporal.ChronoField;
-import java.util.AbstractMap;
-import java.util.Collections;
-import java.util.List;
-import java.util.Map;
-import java.util.Objects;
-import java.util.Optional;
-import java.util.concurrent.ScheduledExecutorService;
-import java.util.concurrent.TimeUnit;
-
/**
* Class representing DDI device connecting directly to hawkBit.
*/
@@ -81,10 +81,10 @@ public class DdiController {
* @param tenant the tenant of the device belongs to
* @param controller the controller
* @param hawkbitClient a factory for creating to {@link DdiRootControllerRestApi} (and used)
- * for communication to hawkBit
+ * for communication to hawkBit
*/
public DdiController(final Tenant tenant, final Controller controller,
- final UpdateHandler updateHandler, final HawkbitClient hawkbitClient) {
+ final UpdateHandler updateHandler, final HawkbitClient hawkbitClient) {
this.tenantId = tenant.getTenantId();
gatewayToken = tenant.getGatewayToken();
downloadAuthenticationEnabled = tenant.isDownloadAuthenticationEnabled();
@@ -112,58 +112,88 @@ public class DdiController {
currentActionId = null;
}
+ public void updateAttribute(final String mode, final String key, final String value) {
+ final DdiUpdateMode updateMode = switch (mode.toLowerCase()) {
+ case "replace" -> DdiUpdateMode.REPLACE;
+ case "remove" -> DdiUpdateMode.REMOVE;
+ default -> DdiUpdateMode.MERGE;
+ };
+
+ final DdiConfigData configData = new DdiConfigData(Collections.singletonMap(key, value), updateMode);
+
+ getDdiApi().putConfigData(configData, getTenantId(), getControllerId());
+ }
+
+ void sendFeedback(final UpdateStatus updateStatus) {
+ log.debug(LOG_PREFIX + "Send feedback {} -> {}", getTenantId(), getControllerId(), currentActionId, updateStatus);
+ try {
+ getDdiApi().postDeploymentBaseActionFeedback(updateStatus.feedback(), getTenantId(), getControllerId(),
+ currentActionId);
+ } catch (final RuntimeException e) {
+ log.error(LOG_PREFIX + "Failed to send feedback {} -> {}", getTenantId(), getControllerId(),
+ currentActionId, updateStatus, e);
+ }
+
+ if (updateStatus.status() == UpdateStatus.Status.SUCCESSFUL ||
+ updateStatus.status() == UpdateStatus.Status.FAILURE) {
+ lastActionId = currentActionId;
+ currentActionId = null;
+ }
+ }
+
private void poll() {
log.debug(LOG_PREFIX + " Polling ...", tenantId, controllerId);
Optional.ofNullable(executorService).ifPresent(executor ->
- getControllerBase().ifPresentOrElse(
- controllerBase -> {
- final Optional confirmationBaseLink = getRequiredLink(controllerBase, CONFIRMATION_BASE_LINK);
- if (confirmationBaseLink.isPresent()) {
- final long actionId = getActionId(confirmationBaseLink.get());
- log.info(LOG_PREFIX + "Confirmation is required for action {}!", getTenantId(),
- getControllerId(), actionId);
- // TODO - confirmation handler
- sendConfirmationFeedback(actionId);
- executor.schedule(this::poll, IMMEDIATE_MS, TimeUnit.MILLISECONDS);
- } else {
- getRequiredLink(controllerBase, DEPLOYMENT_BASE_LINK).flatMap(this::getActionWithDeployment).ifPresentOrElse(actionWithDeployment -> {
- final long actionId = actionWithDeployment.getKey();
- if (currentActionId == null) {
- if (lastActionId != null && lastActionId == actionId) {
- log.info(LOG_PREFIX + "Still receive the last action {}",
- getTenantId(), getControllerId(), actionId);
- return;
- }
+ getControllerBase().ifPresentOrElse(
+ controllerBase -> {
+ final Optional confirmationBaseLink = getRequiredLink(controllerBase, CONFIRMATION_BASE_LINK);
+ if (confirmationBaseLink.isPresent()) {
+ final long actionId = getActionId(confirmationBaseLink.get());
+ log.info(LOG_PREFIX + "Confirmation is required for action {}!", getTenantId(),
+ getControllerId(), actionId);
+ // TODO - confirmation handler
+ sendConfirmationFeedback(actionId);
+ executor.schedule(this::poll, IMMEDIATE_MS, TimeUnit.MILLISECONDS);
+ } else {
+ getRequiredLink(controllerBase, DEPLOYMENT_BASE_LINK).flatMap(this::getActionWithDeployment)
+ .ifPresentOrElse(actionWithDeployment -> {
+ final long actionId = actionWithDeployment.getKey();
+ if (currentActionId == null) {
+ if (lastActionId != null && lastActionId == actionId) {
+ log.info(LOG_PREFIX + "Still receive the last action {}",
+ getTenantId(), getControllerId(), actionId);
+ return;
+ }
- log.info(LOG_PREFIX + "Process action {}", getTenantId(), getControllerId(),
- actionId);
- final DdiDeployment deployment = actionWithDeployment.getValue().getDeployment();
- final DdiDeployment.HandlingType updateType = deployment.getUpdate();
- final List modules = deployment.getChunks();
+ log.info(LOG_PREFIX + "Process action {}", getTenantId(), getControllerId(),
+ actionId);
+ final DdiDeployment deployment = actionWithDeployment.getValue().getDeployment();
+ final DdiDeployment.HandlingType updateType = deployment.getUpdate();
+ final List modules = deployment.getChunks();
- currentActionId = actionId;
- executor.submit(
- updateHandler.getUpdateProcessor(this, updateType, modules));
- } else if (currentActionId != actionId) {
- // TODO - cancel and start new one?
- log.info(LOG_PREFIX + "Action {} is canceled while in process (new {})!", getTenantId(),
- getControllerId(), currentActionId, actionId);
- } // else same action - already processing
- }, () -> {
- if (currentActionId != null) {
- // TODO - cancel current?
- log.info(LOG_PREFIX + "Action {} is canceled while in process (not returned)!", getTenantId(),
- getControllerId(), getCurrentActionId());
- }
- });
- executor.schedule(this::poll, getPollMillis(controllerBase), TimeUnit.MILLISECONDS);
+ currentActionId = actionId;
+ executor.submit(
+ updateHandler.getUpdateProcessor(this, updateType, modules));
+ } else if (currentActionId != actionId) {
+ // TODO - cancel and start new one?
+ log.info(LOG_PREFIX + "Action {} is canceled while in process (new {})!", getTenantId(),
+ getControllerId(), currentActionId, actionId);
+ } // else same action - already processing
+ }, () -> {
+ if (currentActionId != null) {
+ // TODO - cancel current?
+ log.info(LOG_PREFIX + "Action {} is canceled while in process (not returned)!", getTenantId(),
+ getControllerId(), getCurrentActionId());
+ }
+ });
+ executor.schedule(this::poll, getPollMillis(controllerBase), TimeUnit.MILLISECONDS);
+ }
+ },
+ () -> {
+ // error has occurred or no controller base hasn't been acquired
+ executor.schedule(this::poll, DEFAULT_POLL_MS, TimeUnit.MILLISECONDS);
}
- },
- () -> {
- // error has occurred or no controller base hasn't been acquired
- executor.schedule(this::poll, DEFAULT_POLL_MS, TimeUnit.MILLISECONDS);
- }
- ));
+ ));
}
private Optional getControllerBase() {
@@ -211,42 +241,14 @@ public class DdiController {
final ResponseEntity action = getDdiApi()
.getControllerDeploymentBaseAction(getTenantId(), getControllerId(), actionId, -1, null);
if (action.getStatusCode() != HttpStatus.OK) {
- log.warn(LOG_PREFIX + "Fail to get deployment action: {} -> {}", getTenantId(), getControllerId(), actionId, action.getStatusCode());
+ log.warn(LOG_PREFIX + "Fail to get deployment action: {} -> {}", getTenantId(), getControllerId(), actionId,
+ action.getStatusCode());
return Optional.empty();
}
return Optional.ofNullable(action.getBody() == null ? null : new AbstractMap.SimpleEntry<>(actionId, action.getBody()));
}
- public void updateAttribute(final String mode, final String key, final String value) {
- final DdiUpdateMode updateMode = switch (mode.toLowerCase()) {
- case "replace" -> DdiUpdateMode.REPLACE;
- case "remove" -> DdiUpdateMode.REMOVE;
- default -> DdiUpdateMode.MERGE;
- };
-
- final DdiConfigData configData = new DdiConfigData(Collections.singletonMap(key, value), updateMode);
-
- getDdiApi().putConfigData(configData, getTenantId(), getControllerId());
- }
-
- void sendFeedback(final UpdateStatus updateStatus) {
- log.debug(LOG_PREFIX + "Send feedback {} -> {}", getTenantId(), getControllerId(), currentActionId, updateStatus);
- try {
- getDdiApi().postDeploymentBaseActionFeedback(updateStatus.feedback(), getTenantId(), getControllerId(),
- currentActionId);
- } catch (final RuntimeException e) {
- log.error(LOG_PREFIX + "Failed to send feedback {} -> {}", getTenantId(), getControllerId(),
- currentActionId, updateStatus, e);
- }
-
- if (updateStatus.status() == UpdateStatus.Status.SUCCESSFUL ||
- updateStatus.status() == UpdateStatus.Status.FAILURE) {
- lastActionId = currentActionId;
- currentActionId = null;
- }
- }
-
private void sendConfirmationFeedback(final long actionId) {
final DdiConfirmationFeedback ddiConfirmationFeedback = new DdiConfirmationFeedback(
DdiConfirmationFeedback.Confirmation.CONFIRMED, 0, Collections.singletonList(
diff --git a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiTenant.java b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiTenant.java
index 117396006..28387b4fe 100644
--- a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiTenant.java
+++ b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/DdiTenant.java
@@ -9,15 +9,15 @@
*/
package org.eclipse.hawkbit.sdk.device;
+import java.util.Map;
+import java.util.Optional;
+import java.util.concurrent.ConcurrentHashMap;
+
import lombok.Getter;
import org.eclipse.hawkbit.sdk.Controller;
import org.eclipse.hawkbit.sdk.HawkbitClient;
import org.eclipse.hawkbit.sdk.Tenant;
-import java.util.Map;
-import java.util.Optional;
-import java.util.concurrent.ConcurrentHashMap;
-
/**
* An in-memory simulated DDI Tenant to hold the controller twins in
* memory and be able to retrieve them again.
diff --git a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateHandler.java b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateHandler.java
index d3973bd91..057f40ac8 100644
--- a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateHandler.java
+++ b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateHandler.java
@@ -9,6 +9,22 @@
*/
package org.eclipse.hawkbit.sdk.device;
+import java.io.IOException;
+import java.io.InputStream;
+import java.nio.file.Files;
+import java.nio.file.Path;
+import java.security.KeyManagementException;
+import java.security.KeyStoreException;
+import java.security.MessageDigest;
+import java.security.NoSuchAlgorithmException;
+import java.util.ArrayList;
+import java.util.HashMap;
+import java.util.HexFormat;
+import java.util.LinkedList;
+import java.util.List;
+import java.util.Map;
+import java.util.stream.Collectors;
+
import lombok.extern.slf4j.Slf4j;
import org.apache.hc.client5.http.classic.methods.HttpGet;
import org.apache.hc.client5.http.impl.classic.CloseableHttpClient;
@@ -28,22 +44,6 @@ import org.springframework.util.CollectionUtils;
import org.springframework.util.ObjectUtils;
import org.springframework.util.StringUtils;
-import java.io.IOException;
-import java.io.InputStream;
-import java.nio.file.Files;
-import java.nio.file.Path;
-import java.security.KeyManagementException;
-import java.security.KeyStoreException;
-import java.security.MessageDigest;
-import java.security.NoSuchAlgorithmException;
-import java.util.ArrayList;
-import java.util.HashMap;
-import java.util.HexFormat;
-import java.util.LinkedList;
-import java.util.List;
-import java.util.Map;
-import java.util.stream.Collectors;
-
/**
* Update handler provide plug-in endpoint allowing for customization of the update processing.
*/
@@ -67,20 +67,16 @@ public interface UpdateHandler {
@Slf4j
class UpdateProcessor implements Runnable {
+ protected final Map downloads = new HashMap<>();
private static final String LOG_PREFIX = "[{}:{}] ";
-
private static final String DOWNLOAD_LOG_MESSAGE = "Download ";
private static final String EXPECTED = "(Expected: ";
private static final String BUT_GOT_LOG_MESSAGE = " but got: ";
private static final int MINIMUM_TOKEN_LENGTH_FOR_HINT = 6;
-
private final DdiController ddiController;
-
private final DdiDeployment.HandlingType updateType;
private final List modules;
-
private final ArtifactHandler artifactHandler;
- protected final Map downloads = new HashMap<>();
public UpdateProcessor(
final DdiController ddiController,
@@ -186,101 +182,6 @@ public interface UpdateHandler {
log.debug(LOG_PREFIX + "Cleaned up", ddiController.getTenantId(), ddiController.getControllerId());
}
- private void handleArtifact(
- final String targetToken, final String gatewayToken,
- final List status, final DdiArtifact artifact) {
- artifact.getLink("download").ifPresentOrElse(
- // HTTPS
- link -> status.add(downloadUrl(link.getHref(), gatewayToken, targetToken,
- artifact.getHashes(), artifact.getSize())),
- // HTTP
- () -> status.add(downloadUrl(
- artifact.getLink("download-http")
- .map(Link::getHref)
- .orElseThrow(() -> new IllegalArgumentException("Nor https nor http found!")),
- gatewayToken, targetToken,
- artifact.getHashes(), artifact.getSize()))
- );
- }
-
- private UpdateStatus downloadUrl(
- final String url, final String gatewayToken, final String targetToken,
- final DdiArtifactHash hash, final long size) {
- if (log.isDebugEnabled()) {
- log.debug(LOG_PREFIX + "Downloading {} with token {}, expected hash {} and size {}",
- ddiController.getTenantId(), ddiController.getControllerId(), url,
- hideTokenDetails(targetToken), hash, size);
- }
-
- try {
- return readAndCheckDownloadUrl(url, gatewayToken, targetToken, hash, size);
- } catch (final IOException | KeyManagementException | NoSuchAlgorithmException | KeyStoreException e) {
- log.error(LOG_PREFIX + "Failed to download {}",
- ddiController.getTenantId(), ddiController.getControllerId(), url, e);
- return new UpdateStatus(
- UpdateStatus.Status.FAILURE,
- List.of("Failed to download " + url + ": " + e.getMessage()));
- }
- }
-
- private UpdateStatus readAndCheckDownloadUrl(final String url, final String gatewayToken,
- final String targetToken, final DdiArtifactHash hash, final long size)
- throws NoSuchAlgorithmException, KeyStoreException, KeyManagementException, IOException {
- final Validator sizeValidator = sizeValidator(size);
- final Validator hashValidator = hashValidator(hash);
- final ArtifactHandler.DownloadHandler downloadHandler = artifactHandler.getDownloadHandler(url);
-
- try (final CloseableHttpClient httpclient = createHttpClientThatAcceptsAllServerCerts()) {
- final HttpGet request = new HttpGet(url);
- if (StringUtils.hasLength(targetToken)) {
- request.addHeader(HttpHeaders.AUTHORIZATION, "TargetToken " + targetToken);
- } else if (StringUtils.hasLength(gatewayToken)) {
- request.addHeader(HttpHeaders.AUTHORIZATION, "GatewayToken " + gatewayToken);
- }
-
- return httpclient.execute(request, response -> {
- try {
- if (response.getCode() != HttpStatus.OK.value()) {
- throw new IllegalStateException("Unexpected status code: " + response.getCode());
- }
-
- if (response.getEntity().getContentLength() != size) {
- throw new IllegalArgumentException("Wrong content length " + EXPECTED + size + BUT_GOT_LOG_MESSAGE + response.getEntity()
- .getContentLength() + ")!");
- }
-
- final byte[] buff = new byte[32 * 1024];
- try (final InputStream is = response.getEntity().getContent()) {
- for (int read; (read = is.read(buff)) != -1; ) {
- sizeValidator.read(buff, read);
- hashValidator.read(buff, read);
- downloadHandler.read(buff, 0, read);
- }
- }
- sizeValidator.validate();
- hashValidator.validate();
-
- final String message = "Downloaded " + url + " (" + size + " bytes)";
- log.debug(LOG_PREFIX + message, ddiController.getTenantId(), ddiController.getControllerId());
- downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.SUCCESS);
- downloadHandler.download().ifPresent(path -> downloads.put(url, path));
- return new UpdateStatus(UpdateStatus.Status.SUCCESSFUL, List.of(message));
- } catch (final Exception e) {
- final String message = e.getMessage();
- if (log.isTraceEnabled()) {
- log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
- ddiController.getTenantId(), ddiController.getControllerId(), e);
- } else {
- log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
- ddiController.getTenantId(), ddiController.getControllerId());
- }
- downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.ERROR);
- return new UpdateStatus(UpdateStatus.Status.FAILURE, List.of(message));
- }
- });
- }
- }
-
private static String hideTokenDetails(final String targetToken) {
if (targetToken == null) {
return "";
@@ -314,14 +215,6 @@ public interface UpdateHandler {
.build();
}
-
- private interface Validator {
-
- void read(final byte[] buff, final int len);
-
- void validate();
- }
-
private static Validator sizeValidator(final long size) {
return new Validator() {
@@ -384,6 +277,7 @@ public interface UpdateHandler {
}
return new Validator() {
+
@Override
public void read(final byte[] buff, final int len) {
hashValidators.forEach(hashValidator -> hashValidator.update(buff, len));
@@ -395,5 +289,108 @@ public interface UpdateHandler {
}
};
}
+
+ private void handleArtifact(
+ final String targetToken, final String gatewayToken,
+ final List status, final DdiArtifact artifact) {
+ artifact.getLink("download").ifPresentOrElse(
+ // HTTPS
+ link -> status.add(downloadUrl(link.getHref(), gatewayToken, targetToken,
+ artifact.getHashes(), artifact.getSize())),
+ // HTTP
+ () -> status.add(downloadUrl(
+ artifact.getLink("download-http")
+ .map(Link::getHref)
+ .orElseThrow(() -> new IllegalArgumentException("Nor https nor http found!")),
+ gatewayToken, targetToken,
+ artifact.getHashes(), artifact.getSize()))
+ );
+ }
+
+ private UpdateStatus downloadUrl(
+ final String url, final String gatewayToken, final String targetToken,
+ final DdiArtifactHash hash, final long size) {
+ if (log.isDebugEnabled()) {
+ log.debug(LOG_PREFIX + "Downloading {} with token {}, expected hash {} and size {}",
+ ddiController.getTenantId(), ddiController.getControllerId(), url,
+ hideTokenDetails(targetToken), hash, size);
+ }
+
+ try {
+ return readAndCheckDownloadUrl(url, gatewayToken, targetToken, hash, size);
+ } catch (final IOException | KeyManagementException | NoSuchAlgorithmException | KeyStoreException e) {
+ log.error(LOG_PREFIX + "Failed to download {}",
+ ddiController.getTenantId(), ddiController.getControllerId(), url, e);
+ return new UpdateStatus(
+ UpdateStatus.Status.FAILURE,
+ List.of("Failed to download " + url + ": " + e.getMessage()));
+ }
+ }
+
+ private UpdateStatus readAndCheckDownloadUrl(final String url, final String gatewayToken,
+ final String targetToken, final DdiArtifactHash hash, final long size)
+ throws NoSuchAlgorithmException, KeyStoreException, KeyManagementException, IOException {
+ final Validator sizeValidator = sizeValidator(size);
+ final Validator hashValidator = hashValidator(hash);
+ final ArtifactHandler.DownloadHandler downloadHandler = artifactHandler.getDownloadHandler(url);
+
+ try (final CloseableHttpClient httpclient = createHttpClientThatAcceptsAllServerCerts()) {
+ final HttpGet request = new HttpGet(url);
+ if (StringUtils.hasLength(targetToken)) {
+ request.addHeader(HttpHeaders.AUTHORIZATION, "TargetToken " + targetToken);
+ } else if (StringUtils.hasLength(gatewayToken)) {
+ request.addHeader(HttpHeaders.AUTHORIZATION, "GatewayToken " + gatewayToken);
+ }
+
+ return httpclient.execute(request, response -> {
+ try {
+ if (response.getCode() != HttpStatus.OK.value()) {
+ throw new IllegalStateException("Unexpected status code: " + response.getCode());
+ }
+
+ if (response.getEntity().getContentLength() != size) {
+ throw new IllegalArgumentException(
+ "Wrong content length " + EXPECTED + size + BUT_GOT_LOG_MESSAGE + response.getEntity()
+ .getContentLength() + ")!");
+ }
+
+ final byte[] buff = new byte[32 * 1024];
+ try (final InputStream is = response.getEntity().getContent()) {
+ for (int read; (read = is.read(buff)) != -1; ) {
+ sizeValidator.read(buff, read);
+ hashValidator.read(buff, read);
+ downloadHandler.read(buff, 0, read);
+ }
+ }
+ sizeValidator.validate();
+ hashValidator.validate();
+
+ final String message = "Downloaded " + url + " (" + size + " bytes)";
+ log.debug(LOG_PREFIX + message, ddiController.getTenantId(), ddiController.getControllerId());
+ downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.SUCCESS);
+ downloadHandler.download().ifPresent(path -> downloads.put(url, path));
+ return new UpdateStatus(UpdateStatus.Status.SUCCESSFUL, List.of(message));
+ } catch (final Exception e) {
+ final String message = e.getMessage();
+ if (log.isTraceEnabled()) {
+ log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
+ ddiController.getTenantId(), ddiController.getControllerId(), e);
+ } else {
+ log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
+ ddiController.getTenantId(), ddiController.getControllerId());
+ }
+ downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.ERROR);
+ return new UpdateStatus(UpdateStatus.Status.FAILURE, List.of(message));
+ }
+ });
+ }
+ }
+
+ private interface Validator {
+
+ void read(final byte[] buff, final int len);
+
+ void validate();
+ }
}
}
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateStatus.java b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateStatus.java
index d92589858..5d573eb8f 100644
--- a/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateStatus.java
+++ b/hawkbit-sdk/hawkbit-sdk-device/src/main/java/org/eclipse/hawkbit/sdk/device/UpdateStatus.java
@@ -9,14 +9,19 @@
*/
package org.eclipse.hawkbit.sdk.device;
+import java.util.List;
+
import org.eclipse.hawkbit.ddi.json.model.DdiActionFeedback;
import org.eclipse.hawkbit.ddi.json.model.DdiResult;
import org.eclipse.hawkbit.ddi.json.model.DdiStatus;
-import java.util.List;
-
public record UpdateStatus(Status status, List messages) {
+ DdiActionFeedback feedback() {
+ return new DdiActionFeedback(null,
+ new DdiStatus(status.executionStatus, new DdiResult(status.finalResult, null), status.code, messages));
+ }
+
/**
* The status to response to the hawkBit update server if an simulated update process should be respond with
* successful or failure update.
@@ -59,9 +64,4 @@ public record UpdateStatus(Status status, List messages) {
this.code = code;
}
}
-
- DdiActionFeedback feedback() {
- return new DdiActionFeedback(null,
- new DdiStatus(status.executionStatus, new DdiResult(status.finalResult, null), status.code, messages));
- }
}
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/pom.xml b/hawkbit-sdk/hawkbit-sdk-dmf/pom.xml
index 441309f50..0f45717b3 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/pom.xml
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/pom.xml
@@ -10,35 +10,35 @@
-->
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-sdk
- ${revision}
-
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0">
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-sdk
+ ${revision}
+
- hawkbit-sdk-dmf
- hawkBit :: SDK :: DMF SDK
- DMF SDK that could be used for development of DMF integrations on JVM based languages
+ hawkbit-sdk-dmf
+ hawkBit :: SDK :: DMF SDK
+ DMF SDK that could be used for development of DMF integrations on JVM based languages
-
-
- org.eclipse.hawkbit
- hawkbit-sdk-commons
- ${project.version}
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-sdk-commons
+ ${project.version}
+
-
- org.eclipse.hawkbit
- hawkbit-dmf-api
- ${project.version}
-
+
+ org.eclipse.hawkbit
+ hawkbit-dmf-api
+ ${project.version}
+
-
- org.springframework.amqp
- spring-rabbit
-
-
+
+ org.springframework.amqp
+ spring-rabbit
+
+
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfController.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfController.java
index bef946071..977570ef5 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfController.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfController.java
@@ -9,6 +9,10 @@
*/
package org.eclipse.hawkbit.sdk.dmf;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.concurrent.ScheduledExecutorService;
+
import lombok.Getter;
import lombok.Setter;
import lombok.extern.slf4j.Slf4j;
@@ -19,10 +23,6 @@ import org.eclipse.hawkbit.sdk.Controller;
import org.eclipse.hawkbit.sdk.Tenant;
import org.eclipse.hawkbit.sdk.dmf.amqp.DmfSender;
-import java.util.HashMap;
-import java.util.Map;
-import java.util.concurrent.ScheduledExecutorService;
-
/**
* Class representing DMF device twin connecting to hawkBit via DMF.
*/
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfTenant.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfTenant.java
index 9ca753d31..777b1be77 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfTenant.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/DmfTenant.java
@@ -9,6 +9,11 @@
*/
package org.eclipse.hawkbit.sdk.dmf;
+import java.util.Map;
+import java.util.Optional;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.function.BiConsumer;
+
import lombok.Getter;
import org.eclipse.hawkbit.sdk.Controller;
import org.eclipse.hawkbit.sdk.Tenant;
@@ -16,11 +21,6 @@ import org.eclipse.hawkbit.sdk.dmf.amqp.Amqp;
import org.eclipse.hawkbit.sdk.dmf.amqp.VHost;
import org.springframework.amqp.core.Message;
-import java.util.Map;
-import java.util.Optional;
-import java.util.concurrent.ConcurrentHashMap;
-import java.util.function.BiConsumer;
-
/**
* An in-memory simulated DMF Tenant to hold the controller twins in
* memory and be able to retrieve them again.
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateHandler.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateHandler.java
index 1a1fb2c9d..7c8376621 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateHandler.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateHandler.java
@@ -9,6 +9,22 @@
*/
package org.eclipse.hawkbit.sdk.dmf;
+import java.io.IOException;
+import java.io.InputStream;
+import java.nio.file.Files;
+import java.nio.file.Path;
+import java.security.KeyManagementException;
+import java.security.KeyStoreException;
+import java.security.MessageDigest;
+import java.security.NoSuchAlgorithmException;
+import java.util.ArrayList;
+import java.util.HashMap;
+import java.util.HexFormat;
+import java.util.LinkedList;
+import java.util.List;
+import java.util.Map;
+import java.util.stream.Collectors;
+
import lombok.extern.slf4j.Slf4j;
import org.apache.hc.client5.http.classic.methods.HttpGet;
import org.apache.hc.client5.http.impl.classic.CloseableHttpClient;
@@ -29,22 +45,6 @@ import org.springframework.util.CollectionUtils;
import org.springframework.util.ObjectUtils;
import org.springframework.util.StringUtils;
-import java.io.IOException;
-import java.io.InputStream;
-import java.nio.file.Files;
-import java.nio.file.Path;
-import java.security.KeyManagementException;
-import java.security.KeyStoreException;
-import java.security.MessageDigest;
-import java.security.NoSuchAlgorithmException;
-import java.util.ArrayList;
-import java.util.HashMap;
-import java.util.HexFormat;
-import java.util.LinkedList;
-import java.util.List;
-import java.util.Map;
-import java.util.stream.Collectors;
-
/**
* Update handler provide plug-in endpoint allowing for customization of the update processing.
*/
@@ -68,20 +68,16 @@ public interface UpdateHandler {
@Slf4j
class UpdateProcessor implements Runnable {
+ protected final Map downloads = new HashMap<>();
private static final String LOG_PREFIX = "[{}:{}] ";
-
private static final String DOWNLOAD_LOG_MESSAGE = "Download ";
private static final String EXPECTED = "(Expected: ";
private static final String BUT_GOT_LOG_MESSAGE = " but got: ";
private static final int MINIMUM_TOKEN_LENGTH_FOR_HINT = 6;
-
private final DmfController dmfController;
-
private final DmfDownloadAndUpdateRequest updateRequest;
private final EventTopic eventTopic;
-
private final ArtifactHandler artifactHandler;
- protected final Map downloads = new HashMap<>();
public UpdateProcessor(
final DmfController dmfController,
@@ -189,94 +185,6 @@ public interface UpdateHandler {
log.debug(LOG_PREFIX + "Cleaned up", dmfController.getTenantId(), dmfController.getControllerId());
}
- private void handleArtifact(
- final String targetToken,
- final List status, final DmfArtifact artifact) {
- if (artifact.getUrls().containsKey("HTTPS")) {
- status.add(downloadUrl(artifact.getUrls().get("HTTPS"), targetToken,
- artifact.getHashes(), artifact.getSize()));
- } else if (artifact.getUrls().containsKey("HTTP")) {
- status.add(downloadUrl(artifact.getUrls().get("HTTP"), targetToken,
- artifact.getHashes(), artifact.getSize()));
- }
- }
-
- private UpdateStatus downloadUrl(
- final String url, final String targetToken,
- final DmfArtifactHash hash, final long size) {
- if (log.isDebugEnabled()) {
- log.debug(LOG_PREFIX + "Downloading {} with token {}, expected hash {} and size {}",
- dmfController.getTenantId(), dmfController.getControllerId(), url,
- hideTokenDetails(targetToken), hash, size);
- }
-
- try {
- return readAndCheckDownloadUrl(url, targetToken, hash, size);
- } catch (final IOException | KeyManagementException | NoSuchAlgorithmException | KeyStoreException e) {
- log.error(LOG_PREFIX + "Failed to download {}",
- dmfController.getTenantId(), dmfController.getControllerId(), url, e);
- return new UpdateStatus(
- DmfActionStatus.ERROR,
- List.of("Failed to download " + url + ": " + e.getMessage()));
- }
- }
-
- private UpdateStatus readAndCheckDownloadUrl(final String url,
- final String targetToken, final DmfArtifactHash hash, final long size)
- throws NoSuchAlgorithmException, KeyStoreException, KeyManagementException, IOException {
- final Validator sizeValidator = sizeValidator(size);
- final Validator hashValidator = hashValidator(hash);
- final ArtifactHandler.DownloadHandler downloadHandler = artifactHandler.getDownloadHandler(url);
-
- try (final CloseableHttpClient httpclient = createHttpClientThatAcceptsAllServerCerts()) {
- final HttpGet request = new HttpGet(url);
- if (StringUtils.hasLength(targetToken)) {
- request.addHeader(HttpHeaders.AUTHORIZATION, "TargetToken " + targetToken);
- }
-
- return httpclient.execute(request, response -> {
- try {
- if (response.getCode() != HttpStatus.OK.value()) {
- throw new IllegalStateException("Unexpected status code: " + response.getCode());
- }
-
- if (response.getEntity().getContentLength() != size) {
- throw new IllegalArgumentException("Wrong content length " + EXPECTED + size + BUT_GOT_LOG_MESSAGE + response.getEntity()
- .getContentLength() + ")!");
- }
-
- final byte[] buff = new byte[32 * 1024];
- try (final InputStream is = response.getEntity().getContent()) {
- for (int read; (read = is.read(buff)) != -1; ) {
- sizeValidator.read(buff, read);
- hashValidator.read(buff, read);
- downloadHandler.read(buff, 0, read);
- }
- }
- sizeValidator.validate();
- hashValidator.validate();
-
- final String message = "Downloaded " + url + " (" + size + " bytes)";
- log.debug(LOG_PREFIX + message, dmfController.getTenantId(), dmfController.getControllerId());
- downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.SUCCESS);
- downloadHandler.download().ifPresent(path -> downloads.put(url, path));
- return new UpdateStatus(DmfActionStatus.FINISHED, List.of(message));
- } catch (final Exception e) {
- final String message = e.getMessage();
- if (log.isTraceEnabled()) {
- log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
- dmfController.getTenantId(), dmfController.getControllerId(), e);
- } else {
- log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
- dmfController.getTenantId(), dmfController.getControllerId());
- }
- downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.ERROR);
- return new UpdateStatus(DmfActionStatus.ERROR, List.of(message));
- }
- });
- }
- }
-
private static String hideTokenDetails(final String targetToken) {
if (targetToken == null) {
return "";
@@ -310,14 +218,6 @@ public interface UpdateHandler {
.build();
}
-
- private interface Validator {
-
- void read(final byte[] buff, final int len);
-
- void validate();
- }
-
private static Validator sizeValidator(final long size) {
return new Validator() {
@@ -377,6 +277,7 @@ public interface UpdateHandler {
}
return new Validator() {
+
@Override
public void read(final byte[] buff, final int len) {
hashValidators.forEach(hashValidator -> hashValidator.update(buff, len));
@@ -388,5 +289,101 @@ public interface UpdateHandler {
}
};
}
+
+ private void handleArtifact(
+ final String targetToken,
+ final List status, final DmfArtifact artifact) {
+ if (artifact.getUrls().containsKey("HTTPS")) {
+ status.add(downloadUrl(artifact.getUrls().get("HTTPS"), targetToken,
+ artifact.getHashes(), artifact.getSize()));
+ } else if (artifact.getUrls().containsKey("HTTP")) {
+ status.add(downloadUrl(artifact.getUrls().get("HTTP"), targetToken,
+ artifact.getHashes(), artifact.getSize()));
+ }
+ }
+
+ private UpdateStatus downloadUrl(
+ final String url, final String targetToken,
+ final DmfArtifactHash hash, final long size) {
+ if (log.isDebugEnabled()) {
+ log.debug(LOG_PREFIX + "Downloading {} with token {}, expected hash {} and size {}",
+ dmfController.getTenantId(), dmfController.getControllerId(), url,
+ hideTokenDetails(targetToken), hash, size);
+ }
+
+ try {
+ return readAndCheckDownloadUrl(url, targetToken, hash, size);
+ } catch (final IOException | KeyManagementException | NoSuchAlgorithmException | KeyStoreException e) {
+ log.error(LOG_PREFIX + "Failed to download {}",
+ dmfController.getTenantId(), dmfController.getControllerId(), url, e);
+ return new UpdateStatus(
+ DmfActionStatus.ERROR,
+ List.of("Failed to download " + url + ": " + e.getMessage()));
+ }
+ }
+
+ private UpdateStatus readAndCheckDownloadUrl(final String url,
+ final String targetToken, final DmfArtifactHash hash, final long size)
+ throws NoSuchAlgorithmException, KeyStoreException, KeyManagementException, IOException {
+ final Validator sizeValidator = sizeValidator(size);
+ final Validator hashValidator = hashValidator(hash);
+ final ArtifactHandler.DownloadHandler downloadHandler = artifactHandler.getDownloadHandler(url);
+
+ try (final CloseableHttpClient httpclient = createHttpClientThatAcceptsAllServerCerts()) {
+ final HttpGet request = new HttpGet(url);
+ if (StringUtils.hasLength(targetToken)) {
+ request.addHeader(HttpHeaders.AUTHORIZATION, "TargetToken " + targetToken);
+ }
+
+ return httpclient.execute(request, response -> {
+ try {
+ if (response.getCode() != HttpStatus.OK.value()) {
+ throw new IllegalStateException("Unexpected status code: " + response.getCode());
+ }
+
+ if (response.getEntity().getContentLength() != size) {
+ throw new IllegalArgumentException(
+ "Wrong content length " + EXPECTED + size + BUT_GOT_LOG_MESSAGE + response.getEntity()
+ .getContentLength() + ")!");
+ }
+
+ final byte[] buff = new byte[32 * 1024];
+ try (final InputStream is = response.getEntity().getContent()) {
+ for (int read; (read = is.read(buff)) != -1; ) {
+ sizeValidator.read(buff, read);
+ hashValidator.read(buff, read);
+ downloadHandler.read(buff, 0, read);
+ }
+ }
+ sizeValidator.validate();
+ hashValidator.validate();
+
+ final String message = "Downloaded " + url + " (" + size + " bytes)";
+ log.debug(LOG_PREFIX + message, dmfController.getTenantId(), dmfController.getControllerId());
+ downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.SUCCESS);
+ downloadHandler.download().ifPresent(path -> downloads.put(url, path));
+ return new UpdateStatus(DmfActionStatus.FINISHED, List.of(message));
+ } catch (final Exception e) {
+ final String message = e.getMessage();
+ if (log.isTraceEnabled()) {
+ log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
+ dmfController.getTenantId(), dmfController.getControllerId(), e);
+ } else {
+ log.error(LOG_PREFIX + DOWNLOAD_LOG_MESSAGE + url + " failed: " + message,
+ dmfController.getTenantId(), dmfController.getControllerId());
+ }
+ downloadHandler.finished(ArtifactHandler.DownloadHandler.Status.ERROR);
+ return new UpdateStatus(DmfActionStatus.ERROR, List.of(message));
+ }
+ });
+ }
+ }
+
+ private interface Validator {
+
+ void read(final byte[] buff, final int len);
+
+ void validate();
+ }
}
}
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateStatus.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateStatus.java
index 0bf847ae8..b46167f66 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateStatus.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/UpdateStatus.java
@@ -9,8 +9,8 @@
*/
package org.eclipse.hawkbit.sdk.dmf;
-import org.eclipse.hawkbit.dmf.json.model.DmfActionStatus;
-
import java.util.List;
+import org.eclipse.hawkbit.dmf.json.model.DmfActionStatus;
+
public record UpdateStatus(DmfActionStatus status, List messages) {}
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/Amqp.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/Amqp.java
index 122159731..409409bef 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/Amqp.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/Amqp.java
@@ -9,6 +9,10 @@
*/
package org.eclipse.hawkbit.sdk.dmf.amqp;
+import java.security.KeyManagementException;
+import java.security.NoSuchAlgorithmException;
+import java.util.concurrent.ConcurrentHashMap;
+
import lombok.extern.slf4j.Slf4j;
import org.eclipse.hawkbit.sdk.Tenant.DMF;
import org.springframework.amqp.rabbit.connection.CachingConnectionFactory;
@@ -16,10 +20,6 @@ import org.springframework.amqp.rabbit.connection.ConnectionFactory;
import org.springframework.boot.autoconfigure.amqp.RabbitProperties;
import org.springframework.util.ObjectUtils;
-import java.security.KeyManagementException;
-import java.security.NoSuchAlgorithmException;
-import java.util.concurrent.ConcurrentHashMap;
-
/**
* Abstract class for connecting to AMQP host.
*/
@@ -41,7 +41,7 @@ public class Amqp {
public VHost getVhost(final DMF dmf, final boolean initVHost) {
final String vHost = dmf == null || ObjectUtils.isEmpty(dmf.getVirtualHost()) ?
- (rabbitProperties.getVirtualHost() == null ? "/" :rabbitProperties.getVirtualHost()) :
+ (rabbitProperties.getVirtualHost() == null ? "/" : rabbitProperties.getVirtualHost()) :
dmf.getVirtualHost();
return vHosts.computeIfAbsent(vHost, vh -> new VHost(getConnectionFactory(dmf, vHost), amqpProperties, initVHost));
}
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/AmqpProperties.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/AmqpProperties.java
index 902550092..86774cf4b 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/AmqpProperties.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/AmqpProperties.java
@@ -12,7 +12,6 @@ package org.eclipse.hawkbit.sdk.dmf.amqp;
import lombok.Data;
import lombok.ToString;
import org.springframework.boot.context.properties.ConfigurationProperties;
-import org.springframework.stereotype.Component;
/**
* Bean which holds the necessary properties for configuring the AMQP connection.
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/DmfSender.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/DmfSender.java
index 88e0a00cf..3e3cd4cc2 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/DmfSender.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/DmfSender.java
@@ -9,6 +9,8 @@
*/
package org.eclipse.hawkbit.sdk.dmf.amqp;
+import static org.eclipse.hawkbit.dmf.amqp.api.AmqpSettings.DMF_EXCHANGE;
+
import java.util.List;
import java.util.Map;
import java.util.UUID;
@@ -31,17 +33,14 @@ import org.springframework.amqp.rabbit.core.RabbitTemplate;
import org.springframework.amqp.support.converter.AbstractJavaTypeMapper;
import org.springframework.util.ObjectUtils;
-import static org.eclipse.hawkbit.dmf.amqp.api.AmqpSettings.DMF_EXCHANGE;
-
/**
* Sender service to send messages to update server.
*/
@Slf4j
public class DmfSender {
- private static final byte[] EMPTY_BODY = new byte[0];
-
protected final RabbitTemplate rabbitTemplate;
+ private static final byte[] EMPTY_BODY = new byte[0];
private final AmqpProperties amqpProperties;
private final ConcurrentHashMap> pingListeners = new ConcurrentHashMap<>();
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/VHost.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/VHost.java
index 64e2a9d54..f467e6178 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/VHost.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/amqp/VHost.java
@@ -9,6 +9,15 @@
*/
package org.eclipse.hawkbit.sdk.dmf.amqp;
+import java.nio.charset.StandardCharsets;
+import java.time.Duration;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.Map;
+import java.util.Optional;
+import java.util.Set;
+import java.util.concurrent.ConcurrentHashMap;
+
import lombok.extern.slf4j.Slf4j;
import org.eclipse.hawkbit.dmf.amqp.api.EventTopic;
import org.eclipse.hawkbit.dmf.amqp.api.MessageHeaderKey;
@@ -33,24 +42,15 @@ import org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer;
import org.springframework.amqp.support.converter.AbstractJavaTypeMapper;
import org.springframework.amqp.support.converter.Jackson2JsonMessageConverter;
-import java.nio.charset.StandardCharsets;
-import java.time.Duration;
-import java.util.Collections;
-import java.util.HashSet;
-import java.util.Map;
-import java.util.Optional;
-import java.util.Set;
-import java.util.concurrent.ConcurrentHashMap;
-
/**
* Abstract class for sender and receiver service.
*/
@Slf4j
public class VHost extends DmfSender implements MessageListener {
+ private static final String REGEX_EXTRACT_ACTION_ID = "[^0-9]";
private final SimpleMessageListenerContainer container;
private final ConcurrentHashMap dmfTenants = new ConcurrentHashMap<>();
-
private final Set openActions = Collections.synchronizedSet(new HashSet<>());
public VHost(final ConnectionFactory connectionFactory, final AmqpProperties amqpProperties) {
@@ -80,7 +80,7 @@ public class VHost extends DmfSender implements MessageListener {
rabbitAdmin.declareExchange(exchange);
rabbitAdmin.declareBinding(BindingBuilder.bind(queue).to(exchange));
}
-
+
container = new SimpleMessageListenerContainer();
container.setConnectionFactory(connectionFactory);
container.setQueueNames(amqpProperties.getReceiverConnectorQueueFromSp());
@@ -88,11 +88,6 @@ public class VHost extends DmfSender implements MessageListener {
container.start();
}
- void stop() {
- container.stop();
- rabbitTemplate.destroy();
- }
-
public void register(final DmfTenant dmfTenant) {
dmfTenants.put(dmfTenant.getTenant().getTenantId(), dmfTenant);
}
@@ -100,8 +95,8 @@ public class VHost extends DmfSender implements MessageListener {
@Override
public void onMessage(final Message message) {
final String tenantId = getTenant(message);
- final String controllerId = (String)message.getMessageProperties().getHeaders().get(MessageHeaderKey.THING_ID);
- final String type = (String)message.getMessageProperties().getHeaders().get(MessageHeaderKey.TYPE);
+ final String controllerId = (String) message.getMessageProperties().getHeaders().get(MessageHeaderKey.THING_ID);
+ final String type = (String) message.getMessageProperties().getHeaders().get(MessageHeaderKey.TYPE);
log.info("Message received for target {}, value : {}", controllerId, message);
switch (MessageType.valueOf(type)) {
@@ -130,6 +125,62 @@ public class VHost extends DmfSender implements MessageListener {
}
}
+ protected void handleAttributeUpdateRequest(final Message message, final String controllerId) {
+ final String tenantId = getTenant(message);
+ Optional.ofNullable(dmfTenants.get(tenantId))
+ .flatMap(dmfTenant -> dmfTenant.getController(controllerId))
+ .ifPresent(controller ->
+ updateAttributes(tenantId, controllerId, DmfUpdateMode.MERGE, controller.getAttributes()));
+ }
+
+ protected void handleCancelDownloadAction(final Message message, final String thingId) {
+ final String tenant = getTenant(message);
+ final Long actionId = extractActionIdFrom(message);
+
+ processCancelDownloadAction(thingId, tenant, actionId);
+ }
+
+ protected void handleUpdateProcess(final Message message, final String controllerId, final EventTopic actionType) {
+ final String tenant = getTenant(message);
+ final DmfDownloadAndUpdateRequest downloadAndUpdateRequest = convertMessage(message,
+ DmfDownloadAndUpdateRequest.class);
+ dmfTenants.get(tenant).getController(controllerId)
+ .ifPresent(controller -> controller.setCurrentActionId(downloadAndUpdateRequest.getActionId()));
+ processUpdate(tenant, controllerId, actionType, downloadAndUpdateRequest);
+ }
+
+ void stop() {
+ container.stop();
+ rabbitTemplate.destroy();
+ }
+
+ private static String getTenant(final Message message) {
+ final MessageProperties messageProperties = message.getMessageProperties();
+ final Map headers = messageProperties.getHeaders();
+ return (String) headers.get(MessageHeaderKey.TENANT);
+ }
+
+ /**
+ * Method to validate if content type is set in the message properties.
+ *
+ * @param message the message to get validated
+ */
+ private static void checkContentTypeJson(final Message message) {
+ if (message.getBody().length == 0) {
+ return;
+ }
+ final MessageProperties messageProperties = message.getMessageProperties();
+ final String headerContentType = (String) messageProperties.getHeaders().get("content-type");
+ if (null != headerContentType) {
+ messageProperties.setContentType(headerContentType);
+ }
+ final String contentType = messageProperties.getContentType();
+ if (contentType != null && contentType.contains("json")) {
+ return;
+ }
+ throw new AmqpRejectAndDontRequeueException("Content-Type is not JSON compatible");
+ }
+
private void handleEventMessage(final Message message, final String thingId) {
final Object eventHeader = message.getMessageProperties().getHeaders().get(MessageHeaderKey.TOPIC);
if (eventHeader == null) {
@@ -138,27 +189,26 @@ public class VHost extends DmfSender implements MessageListener {
}
// Exception squid:S2259 - Checked before
- @SuppressWarnings({ "squid:S2259" })
- final EventTopic eventTopic = EventTopic.valueOf(eventHeader.toString());
+ @SuppressWarnings({ "squid:S2259" }) final EventTopic eventTopic = EventTopic.valueOf(eventHeader.toString());
switch (eventTopic) {
- case CONFIRM:
- handleConfirmation(message, thingId);
- break;
- case DOWNLOAD_AND_INSTALL, DOWNLOAD:
- handleUpdateProcess(message, thingId, eventTopic);
- break;
- case CANCEL_DOWNLOAD:
- handleCancelDownloadAction(message, thingId);
- break;
- case REQUEST_ATTRIBUTES_UPDATE:
- handleAttributeUpdateRequest(message, thingId);
- break;
- case MULTI_ACTION:
- handleMultiActionRequest(message, thingId);
- break;
- default:
- log.info("No valid event property: {}", eventTopic);
- break;
+ case CONFIRM:
+ handleConfirmation(message, thingId);
+ break;
+ case DOWNLOAD_AND_INSTALL, DOWNLOAD:
+ handleUpdateProcess(message, thingId, eventTopic);
+ break;
+ case CANCEL_DOWNLOAD:
+ handleCancelDownloadAction(message, thingId);
+ break;
+ case REQUEST_ATTRIBUTES_UPDATE:
+ handleAttributeUpdateRequest(message, thingId);
+ break;
+ case MULTI_ACTION:
+ handleMultiActionRequest(message, thingId);
+ break;
+ default:
+ log.info("No valid event property: {}", eventTopic);
+ break;
}
}
@@ -166,7 +216,6 @@ public class VHost extends DmfSender implements MessageListener {
log.warn("Handle confirmed received for {}! Skip it!", controllerId);
}
- private static final String REGEX_EXTRACT_ACTION_ID = "[^0-9]";
private long extractActionIdFrom(final Message message) {
final String messageAsString = message.toString();
final String requiredMessageContent = messageAsString
@@ -191,57 +240,29 @@ public class VHost extends DmfSender implements MessageListener {
openActions.add(actionId);
switch (eventTopic) {
- case DOWNLOAD:
- case DOWNLOAD_AND_INSTALL:
- if (action instanceof DmfDownloadAndUpdateRequest) {
- processUpdate(tenant, controllerId, eventTopic, (DmfDownloadAndUpdateRequest) action);
- }
- break;
- case CANCEL_DOWNLOAD:
- processCancelDownloadAction(controllerId, tenant, action.getActionId());
- break;
- default:
- openActions.remove(actionId);
- log.info("No valid event property in MULTI_ACTION.");
- break;
+ case DOWNLOAD:
+ case DOWNLOAD_AND_INSTALL:
+ if (action instanceof DmfDownloadAndUpdateRequest) {
+ processUpdate(tenant, controllerId, eventTopic, (DmfDownloadAndUpdateRequest) action);
+ }
+ break;
+ case CANCEL_DOWNLOAD:
+ processCancelDownloadAction(controllerId, tenant, action.getActionId());
+ break;
+ default:
+ openActions.remove(actionId);
+ log.info("No valid event property in MULTI_ACTION.");
+ break;
}
}
- protected void handleAttributeUpdateRequest(final Message message, final String controllerId) {
- final String tenantId = getTenant(message);
- Optional.ofNullable(dmfTenants.get(tenantId))
- .flatMap(dmfTenant -> dmfTenant.getController(controllerId))
- .ifPresent(controller ->
- updateAttributes(tenantId, controllerId, DmfUpdateMode.MERGE, controller.getAttributes()));
- }
-
- private static String getTenant(final Message message) {
- final MessageProperties messageProperties = message.getMessageProperties();
- final Map headers = messageProperties.getHeaders();
- return (String) headers.get(MessageHeaderKey.TENANT);
- }
-
- protected void handleCancelDownloadAction(final Message message, final String thingId) {
- final String tenant = getTenant(message);
- final Long actionId = extractActionIdFrom(message);
-
- processCancelDownloadAction(thingId, tenant, actionId);
- }
-
private void processCancelDownloadAction(final String thingId, final String tenant, final Long actionId) {
finishUpdateProcess(thingId, actionId, Collections.singletonList("Simulation canceled"));
openActions.remove(actionId);
}
- protected void handleUpdateProcess(final Message message, final String controllerId, final EventTopic actionType) {
- final String tenant = getTenant(message);
- final DmfDownloadAndUpdateRequest downloadAndUpdateRequest = convertMessage(message,
- DmfDownloadAndUpdateRequest.class);
- dmfTenants.get(tenant).getController(controllerId).ifPresent(controller -> controller.setCurrentActionId(downloadAndUpdateRequest.getActionId()));
- processUpdate(tenant, controllerId, actionType, downloadAndUpdateRequest);
- }
-
- private void processUpdate(final String tenantId, final String controllerId, final EventTopic actionType, final DmfDownloadAndUpdateRequest updateRequest) {
+ private void processUpdate(final String tenantId, final String controllerId, final EventTopic actionType,
+ final DmfDownloadAndUpdateRequest updateRequest) {
Optional.ofNullable(dmfTenants.get(tenantId))
.flatMap(dmfTenant -> dmfTenant.getController(controllerId))
.ifPresent(controller -> controller.processUpdate(actionType, updateRequest));
@@ -257,26 +278,4 @@ public class VHost extends DmfSender implements MessageListener {
clazz.getTypeName());
return (T) rabbitTemplate.getMessageConverter().fromMessage(message);
}
-
- /**
- * Method to validate if content type is set in the message properties.
- *
- * @param message
- * the message to get validated
- */
- private static void checkContentTypeJson(final Message message) {
- if (message.getBody().length == 0) {
- return;
- }
- final MessageProperties messageProperties = message.getMessageProperties();
- final String headerContentType = (String) messageProperties.getHeaders().get("content-type");
- if (null != headerContentType) {
- messageProperties.setContentType(headerContentType);
- }
- final String contentType = messageProperties.getContentType();
- if (contentType != null && contentType.contains("json")) {
- return;
- }
- throw new AmqpRejectAndDontRequeueException("Content-Type is not JSON compatible");
- }
}
\ No newline at end of file
diff --git a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/health/HealthService.java b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/health/HealthService.java
index 110451976..da9ec32ee 100644
--- a/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/health/HealthService.java
+++ b/hawkbit-sdk/hawkbit-sdk-dmf/src/main/java/org/eclipse/hawkbit/sdk/dmf/health/HealthService.java
@@ -9,18 +9,18 @@
*/
package org.eclipse.hawkbit.sdk.dmf.health;
-import org.eclipse.hawkbit.sdk.dmf.DmfTenant;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
-import org.springframework.amqp.core.Message;
-import org.springframework.scheduling.annotation.Scheduled;
-
import java.util.Collection;
import java.util.Collections;
import java.util.HashSet;
import java.util.Set;
import java.util.UUID;
+import org.eclipse.hawkbit.sdk.dmf.DmfTenant;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.springframework.amqp.core.Message;
+import org.springframework.scheduling.annotation.Scheduled;
+
/**
* Handle all incoming Messages from hawkBit update server.
*/
diff --git a/hawkbit-sdk/hawkbit-sdk-mgmt/pom.xml b/hawkbit-sdk/hawkbit-sdk-mgmt/pom.xml
index 15782df13..446fd9765 100644
--- a/hawkbit-sdk/hawkbit-sdk-mgmt/pom.xml
+++ b/hawkbit-sdk/hawkbit-sdk-mgmt/pom.xml
@@ -10,8 +10,8 @@
-->
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0">
4.0.0
diff --git a/hawkbit-sdk/hawkbit-sdk-mgmt/src/main/java/org/eclipse/hawkbit/sdk/mgmt/MgmtApi.java b/hawkbit-sdk/hawkbit-sdk-mgmt/src/main/java/org/eclipse/hawkbit/sdk/mgmt/MgmtApi.java
index c6bc8e8c8..c2df9641f 100644
--- a/hawkbit-sdk/hawkbit-sdk-mgmt/src/main/java/org/eclipse/hawkbit/sdk/mgmt/MgmtApi.java
+++ b/hawkbit-sdk/hawkbit-sdk-mgmt/src/main/java/org/eclipse/hawkbit/sdk/mgmt/MgmtApi.java
@@ -9,6 +9,12 @@
*/
package org.eclipse.hawkbit.sdk.mgmt;
+import java.security.SecureRandom;
+import java.util.Base64;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.Random;
import feign.FeignException;
import lombok.AllArgsConstructor;
@@ -22,13 +28,6 @@ import org.eclipse.hawkbit.sdk.HawkbitClient;
import org.eclipse.hawkbit.sdk.Tenant;
import org.springframework.util.ObjectUtils;
-import java.security.SecureRandom;
-import java.util.Base64;
-import java.util.List;
-import java.util.Map;
-import java.util.Objects;
-import java.util.Random;
-
/**
* Management Api Interface
*/
@@ -39,13 +38,17 @@ public class MgmtApi {
private static final String AUTHENTICATION_MODE_GATEWAY_SECURITY_TOKEN_KEY = "authentication.gatewaytoken.key";
private static final String AUTHENTICATION_MODE_GATEWAY_SECURITY_TOKEN_ENABLED = "authentication.gatewaytoken.enabled";
private static final String AUTHENTICATION_MODE_TARGET_SECURITY_TOKEN_ENABLED = "authentication.targettoken.enabled";
-
-
+ private static final Random RND = new SecureRandom();
@NonNull
private final Tenant tenant;
@NonNull
private final HawkbitClient hawkbitClient;
+ public static String randomToken() {
+ final byte[] rnd = new byte[24];
+ RND.nextBytes(rnd);
+ return Base64.getEncoder().encodeToString(rnd);
+ }
// if gateway toke is configured then the gateway auth is enabled key is set
// so all devices use gateway token authentication
@@ -73,8 +76,8 @@ public class MgmtApi {
}
if (!gatewayToken.equals(
Objects.requireNonNull(mgmtTenantManagementRestApi
- .getTenantConfigurationValue(AUTHENTICATION_MODE_GATEWAY_SECURITY_TOKEN_KEY)
- .getBody()).getValue())) {
+ .getTenantConfigurationValue(AUTHENTICATION_MODE_GATEWAY_SECURITY_TOKEN_KEY)
+ .getBody()).getValue())) {
mgmtTenantManagementRestApi.updateTenantConfiguration(
Map.of(AUTHENTICATION_MODE_GATEWAY_SECURITY_TOKEN_KEY, gatewayToken)
);
@@ -121,11 +124,4 @@ public class MgmtApi {
public void deleteController(final String controllerId) {
hawkbitClient.mgmtService(MgmtTargetRestApi.class, tenant).deleteTarget(controllerId);
}
-
- private static final Random RND = new SecureRandom();
- public static String randomToken() {
- final byte[] rnd = new byte[24];
- RND.nextBytes(rnd);
- return Base64.getEncoder().encodeToString(rnd);
- }
}
\ No newline at end of file
diff --git a/hawkbit-sdk/pom.xml b/hawkbit-sdk/pom.xml
index bd994b569..ad9b8911e 100644
--- a/hawkbit-sdk/pom.xml
+++ b/hawkbit-sdk/pom.xml
@@ -9,8 +9,8 @@
SPDX-License-Identifier: EPL-2.0
-->
-4.0.0
diff --git a/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java b/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java
index ed80da771..5f9891c21 100644
--- a/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java
+++ b/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java
@@ -198,16 +198,6 @@ public final class SpPermission {
public static final String BRACKET_CLOSE = ")";
public static final String HAS_AUTH_PREFIX = "hasAuthority" + BRACKET_OPEN + "'";
public static final String HAS_AUTH_SUFFIX = "'" + BRACKET_CLOSE;
- public static final String HAS_AUTH_AND = " and ";
- /**
- * The role which contains the spring security context in case the
- * system is executing code which is necessary to be privileged.
- */
- public static final String SYSTEM_ROLE = "ROLE_SYSTEM_CODE";
- /**
- * The spring security eval expression operator {@code or}.
- */
- public static final String HAS_AUTH_OR = " or ";
/**
* Spring security eval hasAnyRole expression to check if the spring
* context contains system code role
@@ -387,6 +377,16 @@ public final class SpPermission {
*/
public static final String HAS_AUTH_TENANT_CONFIGURATION = HAS_AUTH_PREFIX + TENANT_CONFIGURATION
+ HAS_AUTH_SUFFIX + HAS_AUTH_OR + IS_SYSTEM_CODE;
+ public static final String HAS_AUTH_AND = " and ";
+ /**
+ * The role which contains the spring security context in case the
+ * system is executing code which is necessary to be privileged.
+ */
+ public static final String SYSTEM_ROLE = "ROLE_SYSTEM_CODE";
+ /**
+ * The spring security eval expression operator {@code or}.
+ */
+ public static final String HAS_AUTH_OR = " or ";
/**
* The role which contains in the spring security context in case an
* controller is authenticated.
diff --git a/hawkbit-starters/README.md b/hawkbit-starters/README.md
index f52f91dfc..a560b8e71 100644
--- a/hawkbit-starters/README.md
+++ b/hawkbit-starters/README.md
@@ -1,5 +1,8 @@
-This is a set of [Spring Boot Starters](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) that allows to quick start a spring boot based application with hawkBit's core functionality.
+This is a set
+of [Spring Boot Starters](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) that
+allows to quick start a spring boot based application with hawkBit's core functionality.
-The [all in one](hawkbit-boot-starter) starter contains the complete feature set in addition we provide four starters for the hawkBit interfaces. They can be combined in any order.
+The [all in one](hawkbit-boot-starter) starter contains the complete feature set in addition we provide four starters
+for the hawkBit interfaces. They can be combined in any order.
Check out the hawkBit [update server](../hawkbit-runtime/hawkbit-update-server) as a reference.
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-ddi-api/README.md b/hawkbit-starters/hawkbit-boot-starter-ddi-api/README.md
index 7a900dfae..bf30adfb6 100644
--- a/hawkbit-starters/hawkbit-boot-starter-ddi-api/README.md
+++ b/hawkbit-starters/hawkbit-boot-starter-ddi-api/README.md
@@ -1 +1,2 @@
-[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for the [Direct Device Integration API](https://www.eclipse.org/hawkbit/documentation/interfaces/ddi-api.html).
\ No newline at end of file
+[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for
+the [Direct Device Integration API](https://www.eclipse.org/hawkbit/documentation/interfaces/ddi-api.html).
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-ddi-api/pom.xml b/hawkbit-starters/hawkbit-boot-starter-ddi-api/pom.xml
index b330ee40b..634843d3f 100644
--- a/hawkbit-starters/hawkbit-boot-starter-ddi-api/pom.xml
+++ b/hawkbit-starters/hawkbit-boot-starter-ddi-api/pom.xml
@@ -9,68 +9,68 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-starters
- ${revision}
-
- hawkbit-boot-starter-ddi-api
- hawkBit :: Spring Boot Starter DDI API
+
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-starters
+ ${revision}
+
+ hawkbit-boot-starter-ddi-api
+ hawkBit :: Spring Boot Starter DDI API
-
-
-
- org.springframework.boot
- spring-boot-starter-web
-
-
- org.springframework.boot
- spring-boot-starter
-
-
- org.springframework.security
- spring-security-web
-
-
- org.springframework.security
- spring-security-config
-
-
- org.springframework.security
- spring-security-aspects
-
-
+
+
+
+ org.springframework.boot
+ spring-boot-starter-web
+
+
+ org.springframework.boot
+ spring-boot-starter
+
+
+ org.springframework.security
+ spring-security-web
+
+
+ org.springframework.security
+ spring-security-config
+
+
+ org.springframework.security
+ spring-security-aspects
+
+
-
-
- org.eclipse.hawkbit
- hawkbit-ddi-resource
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-security-integration
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-http-security
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-jpa
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-autoconfigure
- ${project.version}
-
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-ddi-resource
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-security-integration
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-http-security
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-jpa
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-autoconfigure
+ ${project.version}
+
+
-
+
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-dmf-api/README.md b/hawkbit-starters/hawkbit-boot-starter-dmf-api/README.md
index 6ed433b5c..7059bee9c 100644
--- a/hawkbit-starters/hawkbit-boot-starter-dmf-api/README.md
+++ b/hawkbit-starters/hawkbit-boot-starter-dmf-api/README.md
@@ -1 +1,2 @@
-[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for the [Device Management Federation API (AMQP 0.9)](https://www.eclipse.org/hawkbit/documentation/interfaces/dmf-api.html).
\ No newline at end of file
+[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for
+the [Device Management Federation API (AMQP 0.9)](https://www.eclipse.org/hawkbit/documentation/interfaces/dmf-api.html).
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-dmf-api/pom.xml b/hawkbit-starters/hawkbit-boot-starter-dmf-api/pom.xml
index e2627676f..bc61937ce 100644
--- a/hawkbit-starters/hawkbit-boot-starter-dmf-api/pom.xml
+++ b/hawkbit-starters/hawkbit-boot-starter-dmf-api/pom.xml
@@ -9,49 +9,50 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-starters
- ${revision}
-
- hawkbit-boot-starter-dmf-api
- hawkBit :: Spring Boot Starter DMF API
-
-
-
-
- org.springframework.boot
- spring-boot-starter
-
-
- org.springframework.security
- spring-security-config
-
-
- org.springframework.security
- spring-security-aspects
-
-
+
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-starters
+ ${revision}
+
+ hawkbit-boot-starter-dmf-api
+ hawkBit :: Spring Boot Starter DMF API
-
-
- org.eclipse.hawkbit
- hawkbit-dmf-amqp
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-jpa
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-autoconfigure
- ${project.version}
-
-
+
+
+
+ org.springframework.boot
+ spring-boot-starter
+
+
+ org.springframework.security
+ spring-security-config
+
+
+ org.springframework.security
+ spring-security-aspects
+
+
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-dmf-amqp
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-jpa
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-autoconfigure
+ ${project.version}
+
+
+
+
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-mgmt-api/README.md b/hawkbit-starters/hawkbit-boot-starter-mgmt-api/README.md
index 2202eef70..701ab8589 100644
--- a/hawkbit-starters/hawkbit-boot-starter-mgmt-api/README.md
+++ b/hawkbit-starters/hawkbit-boot-starter-mgmt-api/README.md
@@ -1 +1,2 @@
-[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for the [Management API](https://www.eclipse.org/hawkbit/documentation/interfaces/management-api.html).
\ No newline at end of file
+[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) for
+the [Management API](https://www.eclipse.org/hawkbit/documentation/interfaces/management-api.html).
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter-mgmt-api/pom.xml b/hawkbit-starters/hawkbit-boot-starter-mgmt-api/pom.xml
index 65a422443..8b04c554d 100644
--- a/hawkbit-starters/hawkbit-boot-starter-mgmt-api/pom.xml
+++ b/hawkbit-starters/hawkbit-boot-starter-mgmt-api/pom.xml
@@ -9,68 +9,69 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-starters
- ${revision}
-
- hawkbit-boot-starter-mgmt-api
- hawkBit :: Spring Boot Starter Management API
-
-
-
-
- org.springframework.boot
- spring-boot-starter-web
-
-
- org.springframework.boot
- spring-boot-starter
-
-
- org.springframework.security
- spring-security-web
-
-
- org.springframework.security
- spring-security-config
-
-
- org.springframework.security
- spring-security-aspects
-
-
+
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-starters
+ ${revision}
+
+ hawkbit-boot-starter-mgmt-api
+ hawkBit :: Spring Boot Starter Management API
-
-
- org.eclipse.hawkbit
- hawkbit-mgmt-resource
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-security-integration
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-http-security
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-jpa
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-autoconfigure
- ${project.version}
-
-
+
+
+
+ org.springframework.boot
+ spring-boot-starter-web
+
+
+ org.springframework.boot
+ spring-boot-starter
+
+
+ org.springframework.security
+ spring-security-web
+
+
+ org.springframework.security
+ spring-security-config
+
+
+ org.springframework.security
+ spring-security-aspects
+
+
+
+
+
+ org.eclipse.hawkbit
+ hawkbit-mgmt-resource
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-security-integration
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-http-security
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-jpa
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-autoconfigure
+ ${project.version}
+
+
+
+
-
-
\ No newline at end of file
diff --git a/hawkbit-starters/hawkbit-boot-starter/README.MD b/hawkbit-starters/hawkbit-boot-starter/README.MD
index aa57f584a..a1ba4b0ff 100644
--- a/hawkbit-starters/hawkbit-boot-starter/README.MD
+++ b/hawkbit-starters/hawkbit-boot-starter/README.MD
@@ -1,4 +1,5 @@
-[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) including all four interfaces:
+[Spring Boot Starter](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter) including
+all four interfaces:
* [Management API](https://www.eclipse.org/hawkbit/documentation/interfaces/management-api.html)
* [Direct Device Integration API](https://www.eclipse.org/hawkbit/documentation/interfaces/ddi-api.html)
diff --git a/hawkbit-starters/hawkbit-boot-starter/pom.xml b/hawkbit-starters/hawkbit-boot-starter/pom.xml
index 66c12f9d1..4a62b5f58 100644
--- a/hawkbit-starters/hawkbit-boot-starter/pom.xml
+++ b/hawkbit-starters/hawkbit-boot-starter/pom.xml
@@ -9,33 +9,33 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-starters
- ${revision}
-
- hawkbit-boot-starter
- hawkBit :: Spring Boot Starter
- Complete starter, including auto-configuration, logging and all hawkBit interfaces
+
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-starters
+ ${revision}
+
+ hawkbit-boot-starter
+ hawkBit :: Spring Boot Starter
+ Complete starter, including auto-configuration, logging and all hawkBit interfaces
-
-
- org.eclipse.hawkbit
- hawkbit-boot-starter-ddi-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-boot-starter-dmf-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-boot-starter-mgmt-api
- ${project.version}
-
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-boot-starter-ddi-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-boot-starter-dmf-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-boot-starter-mgmt-api
+ ${project.version}
+
+
\ No newline at end of file
diff --git a/hawkbit-starters/pom.xml b/hawkbit-starters/pom.xml
index 45e7ef304..e7decc60b 100644
--- a/hawkbit-starters/pom.xml
+++ b/hawkbit-starters/pom.xml
@@ -9,21 +9,21 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-parent
- ${revision}
-
- hawkbit-starters
- hawkBit :: Spring Boot Starters
- pom
-
- hawkbit-boot-starter
- hawkbit-boot-starter-mgmt-api
- hawkbit-boot-starter-ddi-api
- hawkbit-boot-starter-dmf-api
-
+
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-parent
+ ${revision}
+
+ hawkbit-starters
+ hawkBit :: Spring Boot Starters
+ pom
+
+ hawkbit-boot-starter
+ hawkbit-boot-starter-mgmt-api
+ hawkbit-boot-starter-ddi-api
+ hawkbit-boot-starter-dmf-api
+
\ No newline at end of file
diff --git a/hawkbit-test-report/pom.xml b/hawkbit-test-report/pom.xml
index 7d6e27d8a..4af2916cc 100644
--- a/hawkbit-test-report/pom.xml
+++ b/hawkbit-test-report/pom.xml
@@ -9,185 +9,185 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
-
- org.eclipse.hawkbit
- hawkbit-parent
- ${revision}
-
- hawkbit-test-report
- hawkBit :: Test Report
+ 4.0.0
+
+ org.eclipse.hawkbit
+ hawkbit-parent
+ ${revision}
+
+ hawkbit-test-report
+ hawkBit :: Test Report
-
-
- org.eclipse.hawkbit
- hawkbit-core
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-security-core
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-security-integration
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-http-security
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-core
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-repository-jpa
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-artifact-repository-filesystem
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-autoconfigure
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-ddi-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-ddi-resource
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-mgmt-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-mgmt-resource
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-rest-core
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-dmf-amqp
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-dmf-api
- ${project.version}
-
-
- org.eclipse.hawkbit
- hawkbit-update-server
- ${project.version}
-
-
+
+
+ org.eclipse.hawkbit
+ hawkbit-core
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-security-core
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-security-integration
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-http-security
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-core
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-repository-jpa
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-artifact-repository-filesystem
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-autoconfigure
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-ddi-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-ddi-resource
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-mgmt-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-mgmt-resource
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-rest-core
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-dmf-amqp
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-dmf-api
+ ${project.version}
+
+
+ org.eclipse.hawkbit
+ hawkbit-update-server
+ ${project.version}
+
+
-
-
+
+
-
- org.jacoco
- jacoco-maven-plugin
-
-
- aggregate-reports
- verify
-
- report-aggregate
-
-
- ${jacoco.outputDir}/jacoco-aggregate
-
-
-
-
-
-
-
-
-
-
- generateTestReport
-
-
-
- maven-resources-plugin
-
-
- copy-resources
+
+ org.jacoco
+ jacoco-maven-plugin
+
+
+ aggregate-reportsverify
- copy-resources
+ report-aggregate
- ${basedir}/target/allure-results
-
-
- ${basedir}/..
- false
-
- **/target/allure-results/*.json
-
-
-
- ${basedir}
- false
-
- placeholder.txt
-
-
-
+ ${jacoco.outputDir}/jacoco-aggregate
-
-
-
-
- org.apache.maven.plugins
- maven-assembly-plugin
-
-
- src/main/resources/assemblies/test-report.xml
-
- true
-
-
-
- create-report-zip-assembly
- verify
-
- single
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+ generateTestReport
+
+
+
+ maven-resources-plugin
+
+
+ copy-resources
+ verify
+
+ copy-resources
+
+
+ ${basedir}/target/allure-results
+
+
+ ${basedir}/..
+ false
+
+ **/target/allure-results/*.json
+
+
+
+ ${basedir}
+ false
+
+ placeholder.txt
+
+
+
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-assembly-plugin
+
+
+ src/main/resources/assemblies/test-report.xml
+
+ true
+
+
+
+ create-report-zip-assembly
+ verify
+
+ single
+
+
+
+
+
+
+
+
diff --git a/hawkbit-test-report/src/main/resources/assemblies/test-report.xml b/hawkbit-test-report/src/main/resources/assemblies/test-report.xml
index 974d6b6d1..1f8f96370 100644
--- a/hawkbit-test-report/src/main/resources/assemblies/test-report.xml
+++ b/hawkbit-test-report/src/main/resources/assemblies/test-report.xml
@@ -9,18 +9,19 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- testReport
- /
- false
-
- zip
-
-
-
- ${project.build.directory}/allure-results
- /
-
-
+
+ testReport
+ /
+ false
+
+ zip
+
+
+
+ ${project.build.directory}/allure-results
+ /
+
+
diff --git a/intellij_codeformatter.xml b/intellij_codeformatter.xml
index bc9c7bdb1..dbbcabc9e 100644
--- a/intellij_codeformatter.xml
+++ b/intellij_codeformatter.xml
@@ -1,421 +1,421 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GETTERS_AND_SETTERS
- KEEP
-
-
- OVERRIDDEN_METHODS
- KEEP
-
-
-
-
-
-
-
- true
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
- true
-
-
-
-
-
-
- true
-
-
-
-
-
-
- true
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- true
- true
-
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
-
- true
- method
- true
-
-
-
-
-
-
-
-
- true
-
-
-
-
-
-
- true
-
-
-
-
-
-
-
- true
- true
-
-
-
-
-
-
-
- true
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ GETTERS_AND_SETTERS
+ KEEP
+
+
+ OVERRIDDEN_METHODS
+ KEEP
+
+
+
+
+
+
+
+ true
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+ true
+
+
+
+
+
+
+ true
+
+
+
+
+
+
+ true
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+
+ true
+ method
+ true
+
+
+
+
+
+
+
+
+ true
+
+
+
+
+
+
+ true
+
+
+
+
+
+
+
+ true
+ true
+
+
+
+
+
+
+
+ true
+
+
+
+
+
+
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index c7174fc36..0f3898264 100644
--- a/pom.xml
+++ b/pom.xml
@@ -9,795 +9,797 @@
SPDX-License-Identifier: EPL-2.0
-->
-
- 4.0.0
+ 4.0.0
-
- org.springframework.boot
- spring-boot-starter-parent
- 3.3.5
-
+
+ org.springframework.boot
+ spring-boot-starter-parent
+ 3.3.5
+
- org.eclipse.hawkbit
- hawkbit-parent
- ${revision}
- pom
- hawkBit :: Parent
+ org.eclipse.hawkbit
+ hawkbit-parent
+ ${revision}
+ pom
+ hawkBit :: Parent
-
-
- EPL-2.0
- https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt
- Eclipse Public License - Version 2.0
-
-
+
+
+ EPL-2.0
+ https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt
+ Eclipse Public License - Version 2.0
+
+
-
- 0-SNAPSHOT
- 17
+
+ 0-SNAPSHOT
+ 17
- true
+ true
- 3.3.5
- 2023.0.2
- 2.6.0
- 3.0.0
-
-
-
+ 3.3.5
+ 2023.0.2
+ 2.6.0
+ 3.0.0
+
+
+
-
-
- 4.0.3
-
- 3.0.1
-
+
+
+ 4.0.3
+
+ 3.0.1
+
-
- 9.2.1
- 1.18.1
- 2.3.1
- 3.0.0
- 2.1.0
- 2.16.1
- 4.4
- 1.8.0
-
- 5.2.0
- 4.8.174
- 2.28.1
- 4.2.1
-
+
+ 9.2.1
+ 1.18.1
+ 2.3.1
+ 3.0.0
+ 2.1.0
+ 2.16.1
+ 4.4
+ 1.8.0
+
+ 5.2.0
+ 4.8.174
+ 2.28.1
+ 4.2.1
+
-
- 3.5.0
- 1.6.0
- 2.1.0
- 3.12.1
+
+ 3.5.0
+ 1.6.0
+ 2.1.0
+ 3.12.1
- 1.1.0
- 4.5
+ 1.1.0
+ 4.5
- 3.3.1
- 3.3.1
- 0.8.12
+ 3.3.1
+ 3.3.1
+ 0.8.12
- 1.7.0
- 3.2.4
-
+ 1.7.0
+ 3.2.4
+
-
- scm:git:git@github.com:eclipse/hawkbit.git
- scm:git:https://github.com/eclipse-hawkbit/hawkbit.git
- https://github.com/eclipse-hawkbit/hawkbit.git
-
+
+ scm:git:git@github.com:eclipse/hawkbit.git
+ scm:git:https://github.com/eclipse-hawkbit/hawkbit.git
+
+ https://github.com/eclipse-hawkbit/hawkbit.git
+
-
- https://sonarcloud.io
- LOCAL_SCAN
- true
- 600
- https://www.eclipse.org/hawkbit
- https://github.com/eclipse-hawkbit/hawkbit/actions
-
- **/target/generated-sources/apt/**,**/src/test/**,**/src/main/java/org/eclipse/hawkbit/repository/test/**
-
-
- **/src/main/java/org/eclipse/hawkbit/ui/**,**/target/generated-sources/apt/**,**/src/main/java/org/eclipse/hawkbit/repository/test/**,**/examples/**
-
- ${project.build.directory}
-
- ${project.basedir}/../hawkbit-test-report/target/jacoco-aggregate/jacoco.xml,
- ${project.basedir}/../../hawkbit-test-report/target/jacoco-aggregate/jacoco.xml
-
-
+
+ https://sonarcloud.io
+ LOCAL_SCAN
+ true
+ 600
+ https://www.eclipse.org/hawkbit
+ https://github.com/eclipse-hawkbit/hawkbit/actions
+
+ **/target/generated-sources/apt/**,**/src/test/**,**/src/main/java/org/eclipse/hawkbit/repository/test/**
+
+
+ **/src/main/java/org/eclipse/hawkbit/ui/**,**/target/generated-sources/apt/**,**/src/main/java/org/eclipse/hawkbit/repository/test/**,**/examples/**
+
+ ${project.build.directory}
+
+ ${project.basedir}/../hawkbit-test-report/target/jacoco-aggregate/jacoco.xml,
+ ${project.basedir}/../../hawkbit-test-report/target/jacoco-aggregate/jacoco.xml
+
+
-
- true
- true
- iot.hawkbit
- ${project.build.directory}/dash/summary
-
- ${project.build.directory}/dash/review-summary
- org.eclipse,org.junit
-
+
+ true
+ true
+ iot.hawkbit
+ ${project.build.directory}/dash/summary
+
+ ${project.build.directory}/dash/review-summary
+ org.eclipse,org.junit
+
-
- 1
-
-
-
+
+ 1
+
+
+
-
- hawkbit-core
- hawkbit-security-core
- hawkbit-security-integration
- hawkbit-http-security
- hawkbit-repository
- hawkbit-artifact-repository-filesystem
- hawkbit-autoconfigure
- hawkbit-rest
- hawkbit-dmf
- hawkbit-test-report
- hawkbit-runtime
- hawkbit-starters
- hawkbit-sdk
-
+
+ hawkbit-core
+ hawkbit-security-core
+ hawkbit-security-integration
+ hawkbit-http-security
+ hawkbit-repository
+ hawkbit-artifact-repository-filesystem
+ hawkbit-autoconfigure
+ hawkbit-rest
+ hawkbit-dmf
+ hawkbit-test-report
+ hawkbit-runtime
+ hawkbit-starters
+ hawkbit-sdk
+
-
- ${release.scm.connection}
- ${release.scm.developerConnection}
- ${release.scm.url}
-
+
+ ${release.scm.connection}
+ ${release.scm.developerConnection}
+ ${release.scm.url}
+
-
- Jenkins
- https://hudson.eclipse.org/hawkbit/
-
+
+ Jenkins
+ https://hudson.eclipse.org/hawkbit/
+
-
-
- kaizimmerm
- kai.zimmermann@microsoft.com
- Microsoft
- https://www.microsoft.com
-
- Lead
- Committer
-
-
-
- laverman
- Jeroen.Laverman@bosch.io
- Bosch.IO GmbH
- https://www.bosch.io
-
- Lead
- Committer
-
-
-
- michahirsch
-
- Committer
-
-
-
- schabdo
- Dominic.Schabel@bosch.io
- Bosch.IO GmbH
- https://www.bosch.io
-
- Committer
-
-
-
- stefbehl
- Stefan.Behl@bosch.io
- Bosch.IO GmbH
- https://www.bosch.io
-
- Committer
-
-
-
- avgustinmm
- Avgustin.Marinov@bosch.com
- Bosch Digital
- https://www.bosch-digital.com/
-
- Committer
-
-
-
+
+
+ kaizimmerm
+ kai.zimmermann@microsoft.com
+ Microsoft
+ https://www.microsoft.com
+
+ Lead
+ Committer
+
+
+
+ laverman
+ Jeroen.Laverman@bosch.io
+ Bosch.IO GmbH
+ https://www.bosch.io
+
+ Lead
+ Committer
+
+
+
+ michahirsch
+
+ Committer
+
+
+
+ schabdo
+ Dominic.Schabel@bosch.io
+ Bosch.IO GmbH
+ https://www.bosch.io
+
+ Committer
+
+
+
+ stefbehl
+ Stefan.Behl@bosch.io
+ Bosch.IO GmbH
+ https://www.bosch.io
+
+ Committer
+
+
+
+ avgustinmm
+ Avgustin.Marinov@bosch.com
+ Bosch Digital
+ https://www.bosch-digital.com/
+
+ Committer
+
+
+
-
-
- ossrh
- hawkBit Repository - Release
- https://oss.sonatype.org/service/local/staging/deploy/maven2
-
-
- ossrh
- hawkBit Repository - Snapshots
- https://oss.sonatype.org/content/repositories/snapshots
-
-
+
+
+ ossrh
+ hawkBit Repository - Release
+ https://oss.sonatype.org/service/local/staging/deploy/maven2
+
+
+ ossrh
+ hawkBit Repository - Snapshots
+ https://oss.sonatype.org/content/repositories/snapshots
+
+
-
-
- dash-licenses
- https://repo.eclipse.org/content/repositories/dash-licenses
-
-
+
+
+ dash-licenses
+ https://repo.eclipse.org/content/repositories/dash-licenses
+
+
-
-
-
- org.apache.maven.plugins
- maven-compiler-plugin
-
-
- org.apache.maven.plugins
- maven-source-plugin
-
-
- org.apache.maven.plugins
- maven-enforcer-plugin
-
-
- org.codehaus.mojo
- flatten-maven-plugin
-
-
- org.apache.maven.plugins
- maven-scm-plugin
-
-
- org.codehaus.mojo
- versions-maven-plugin
-
-
-
- com.mycila
- license-maven-plugin
-
-
- org.eclipse.dash
- license-tool-plugin
-
-
-
- org.jacoco
- jacoco-maven-plugin
-
-
-
-
-
+
+
- org.apache.maven.plugins
- maven-compiler-plugin
-
- -Xlint:all
- true
- true
-
+ org.apache.maven.plugins
+ maven-compiler-plugin
- org.apache.maven.plugins
- maven-javadoc-plugin
-
- syntax
-
+ org.apache.maven.plugins
+ maven-source-plugin
- org.apache.maven.plugins
- maven-source-plugin
-
-
- attach-sources
-
- jar
-
-
-
+ org.apache.maven.plugins
+ maven-enforcer-plugin
+
+
+ org.codehaus.mojo
+ flatten-maven-plugin
+
+
+ org.apache.maven.plugins
+ maven-scm-plugin
+
+
+ org.codehaus.mojo
+ versions-maven-plugin
- org.apache.maven.plugins
- maven-enforcer-plugin
- ${maven.enforcer.plugin.version}
-
-
-
- enforce-no-snapshots
-
- enforce
-
-
- ${snapshotDependencyAllowed}
-
-
- No Snapshots Allowed!
-
-
- No Snapshots Allowed!
-
-
- 3.9
-
-
-
-
-
+ com.mycila
+ license-maven-plugin
- org.codehaus.mojo
- flatten-maven-plugin
- ${flatten.maven.plugin.version}
-
- resolveCiFriendliesOnly
- true
-
-
-
- flatten
- process-resources
-
- flatten
-
-
-
- flatten.clean
- clean
-
- clean
-
-
-
-
-
- org.apache.maven.plugins
- maven-scm-plugin
- ${maven.scm.plugin.version}
-
- ${project.version}
-
-
-
- org.apache.maven.plugins
- maven-site-plugin
- ${maven.site.plugin.version}
-
- true
- true
-
+ org.eclipse.dash
+ license-tool-plugin
- com.mycila
- license-maven-plugin
- ${license.maven.plugin.version}
-
-
-
- licenses/LICENSE_HEADER_TEMPLATE.txt
-
- licenses/LICENSE_HEADER_TEMPLATE_CONTRIBUTORS_23.txt
- licenses/LICENSE_HEADER_TEMPLATE_SIEMENS.txt
- licenses/LICENSE_HEADER_TEMPLATE_SIEMENS_18.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_15.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_18.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_19.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_20.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_21.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_22.txt
- licenses/LICENSE_HEADER_TEMPLATE_BOSCH_23.txt
- licenses/LICENSE_HEADER_TEMPLATE_MICROSOFT_18.txt
- licenses/LICENSE_HEADER_TEMPLATE_MICROSOFT_20.txt
- licenses/LICENSE_HEADER_TEMPLATE_DEVOLO_19.txt
- licenses/LICENSE_HEADER_TEMPLATE_DEVOLO_20.txt
- licenses/LICENSE_HEADER_TEMPLATE_KIWIGRID_19.txt
- licenses/LICENSE_HEADER_TEMPLATE_ENAPTER.txt
-
+ org.jacoco
+ jacoco-maven-plugin
+
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-compiler-plugin
+
+ -Xlint:all
+ true
+ true
+
+
+
+ org.apache.maven.plugins
+ maven-javadoc-plugin
+
+ syntax
+
+
+
+ org.apache.maven.plugins
+ maven-source-plugin
+
+
+ attach-sources
+
+ jar
+
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-enforcer-plugin
+ ${maven.enforcer.plugin.version}
+
+
+
+ enforce-no-snapshots
+
+ enforce
+
+
+ ${snapshotDependencyAllowed}
+
+
+ No Snapshots Allowed!
+
+
+ No Snapshots Allowed!
+
+
+ 3.9
+
+
+
+
+
+
+
+ org.codehaus.mojo
+ flatten-maven-plugin
+ ${flatten.maven.plugin.version}
+
+ resolveCiFriendliesOnly
+ true
+
+
+
+ flatten
+ process-resources
+
+ flatten
+
+
+
+ flatten.clean
+ clean
+
+ clean
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-scm-plugin
+ ${maven.scm.plugin.version}
+
+ ${project.version}
+
+
+
+ org.apache.maven.plugins
+ maven-site-plugin
+ ${maven.site.plugin.version}
+
+ true
+ true
+
+
+
+
+ com.mycila
+ license-maven-plugin
+ ${license.maven.plugin.version}
+
+
+
+ licenses/LICENSE_HEADER_TEMPLATE.txt
+
+ licenses/LICENSE_HEADER_TEMPLATE_CONTRIBUTORS_23.txt
+ licenses/LICENSE_HEADER_TEMPLATE_SIEMENS.txt
+ licenses/LICENSE_HEADER_TEMPLATE_SIEMENS_18.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_15.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_18.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_19.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_20.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_21.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_22.txt
+ licenses/LICENSE_HEADER_TEMPLATE_BOSCH_23.txt
+ licenses/LICENSE_HEADER_TEMPLATE_MICROSOFT_18.txt
+ licenses/LICENSE_HEADER_TEMPLATE_MICROSOFT_20.txt
+ licenses/LICENSE_HEADER_TEMPLATE_DEVOLO_19.txt
+ licenses/LICENSE_HEADER_TEMPLATE_DEVOLO_20.txt
+ licenses/LICENSE_HEADER_TEMPLATE_KIWIGRID_19.txt
+ licenses/LICENSE_HEADER_TEMPLATE_ENAPTER.txt
+
+
+ .3rd-party/**
+ .azure-pipelines/*
+ .devcontainer/*
+ .git*
+ .github/**
+ .sonar
+ licenses/LICENSE*
+ eclipse_codeformatter.xml
+ intellij_codeformatter.xml
+ **/banner.txt
+ **/helm/**
+ **/README
+ **/.git*
+ **/*.sql
+ **/docker/**
+ **/.sonar/**
+ **/frontend/**
+ site/content/**
+ site/layouts/**
+ site/static/**
+ site/*.toml
+ **/spring.factories
+
+
+
+
+ JAVADOC_STYLE
+ JAVADOC_STYLE
+
+
+
+
+ org.eclipse.dash
+ license-tool-plugin
+ ${license.tool.plugin.version}
+
+
+ license-check
+
+ license-check
+
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-surefire-plugin
+ ${maven.surefire.plugin.version}
+
+
+
+ ${project.build.directory}/allure-results
+
+
+ 650
+
+
+ false
+ true
+ ${surefire.forkcount}
+ ${jacoco.agent.ut.arg} ${test.jvm.args}
+
+
+ listener
+ io.qameta.allure.junit5.AllureJunit5
+
+
+
+ **/*Tests.java
+ **/*Test.java
+ **/*IT.java
+
- .3rd-party/**
- .azure-pipelines/*
- .devcontainer/*
- .git*
- .github/**
- .sonar
- licenses/LICENSE*
- eclipse_codeformatter.xml
- intellij_codeformatter.xml
- **/banner.txt
- **/helm/**
- **/README
- **/.git*
- **/*.sql
- **/docker/**
- **/.sonar/**
- **/frontend/**
- site/content/**
- site/layouts/**
- site/static/**
- site/*.toml
- **/spring.factories
+ **/Abstract*.java
-
-
-
- JAVADOC_STYLE
- JAVADOC_STYLE
-
-
-
-
- org.eclipse.dash
- license-tool-plugin
- ${license.tool.plugin.version}
-
-
- license-check
-
- license-check
-
-
-
-
-
-
- org.apache.maven.plugins
- maven-surefire-plugin
- ${maven.surefire.plugin.version}
-
-
-
- ${project.build.directory}/allure-results
-
- 650
-
-
- false
- true
- ${surefire.forkcount}
- ${jacoco.agent.ut.arg} ${test.jvm.args}
-
-
- listener
- io.qameta.allure.junit5.AllureJunit5
-
-
-
- **/*Tests.java
- **/*Test.java
- **/*IT.java
-
-
- **/Abstract*.java
-
-
-
-
- org.apache.maven.plugins
- maven-failsafe-plugin
- ${maven.failsafe.plugin.version}
-
- false
- ${surefire.forkcount}
- -Xmx1024m ${jacoco.agent.ut.arg}
-
-
- listener
- io.qameta.allure.junit5.AllureJunit5
-
-
-
-
-
- integration-test
- integration-test
-
- integration-test
-
-
-
-
-
- org.jacoco
- jacoco-maven-plugin
- ${jacoco.maven.plugin.version}
-
-
- prepare-ut-agent
- process-test-classes
-
- prepare-agent
-
-
- jacoco.agent.ut.arg
-
-
-
- prepare-it-agent
- pre-integration-test
-
- prepare-agent-integration
-
-
- jacoco.agent.it.arg
-
-
-
-
-
- com.ethlo.persistence.tools
- eclipselink-maven-plugin
- ${eclipselink.maven.plugin.version}
-
-
-
-
-
-
-
- nexus_staging
-
-
- !skipNexusStaging
-
-
-
-
-
-
- org.sonatype.plugins
- nexus-staging-maven-plugin
- ${nexus.staging.maven.plugin.version}
- true
-
- ossrh
- https://oss.sonatype.org/
- false
-
-
+
+
+
+ org.apache.maven.plugins
+ maven-failsafe-plugin
+ ${maven.failsafe.plugin.version}
+
+ false
+ ${surefire.forkcount}
+ -Xmx1024m ${jacoco.agent.ut.arg}
+
+
+ listener
+ io.qameta.allure.junit5.AllureJunit5
+
+
+
+
+
+ integration-test
+ integration-test
+
+ integration-test
+
+
+
+
+
+ org.jacoco
+ jacoco-maven-plugin
+ ${jacoco.maven.plugin.version}
+
+
+ prepare-ut-agent
+ process-test-classes
+
+ prepare-agent
+
+
+ jacoco.agent.ut.arg
+
+
+
+ prepare-it-agent
+ pre-integration-test
+
+ prepare-agent-integration
+
+
+ jacoco.agent.it.arg
+
+
+
+
+
+ com.ethlo.persistence.tools
+ eclipselink-maven-plugin
+ ${eclipselink.maven.plugin.version}
+
-
-
-
-
- create_gpg_signature
-
- false
-
- createGPGSignature
-
-
-
-
-
- org.apache.maven.plugins
- maven-gpg-plugin
- ${maven.gpg.plugin.version}
-
-
- sign-artifacts
- verify
-
- sign
-
+
+
+
+
+
+ nexus_staging
+
+
+ !skipNexusStaging
+
+
+
+
+
+
+ org.sonatype.plugins
+ nexus-staging-maven-plugin
+ ${nexus.staging.maven.plugin.version}
+ true
-
- --pinentry-mode
- loopback
-
+ ossrh
+ https://oss.sonatype.org/
+ false
-
-
-
-
-
-
-
+
+
+
+
+
+
+ create_gpg_signature
+
+ false
+
+ createGPGSignature
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-gpg-plugin
+ ${maven.gpg.plugin.version}
+
+
+ sign-artifacts
+ verify
+
+ sign
+
+
+
+ --pinentry-mode
+ loopback
+
+
+
+
+
+
+
+
+
-
-
-
-
- com.rabbitmq
- http-client
- ${rabbitmq.http-client.version}
-
-
- com.cronutils
- cron-utils
- ${cron-utils.version}
-
-
- org.jsoup
- jsoup
- ${jsoup.version}
-
-
- javax.el
- javax.el-api
- ${javax.el-api.version}
-
-
- javax.xml.bind
- jaxb-api
- ${jaxb-api.version}
-
+
+
+
+
+ com.rabbitmq
+ http-client
+ ${rabbitmq.http-client.version}
+
+
+ com.cronutils
+ cron-utils
+ ${cron-utils.version}
+
+
+ org.jsoup
+ jsoup
+ ${jsoup.version}
+
+
+ javax.el
+ javax.el-api
+ ${javax.el-api.version}
+
+
+ javax.xml.bind
+ jaxb-api
+ ${jaxb-api.version}
+
-
-
- org.springframework.cloud
- spring-cloud-dependencies
- ${spring.cloud.version}
- pom
- import
-
-
- org.springframework.boot
- spring-boot-starter-web
- ${spring.boot.version}
-
-
- com.fasterxml.jackson.datatype
- jackson-datatype-jdk8
-
-
- com.fasterxml.jackson.datatype
- jackson-datatype-jsr310
-
-
- com.fasterxml.jackson.module
- jackson-module-parameter-names
-
-
-
-
- org.springframework.boot
- spring-boot-starter-tomcat
- ${spring.boot.version}
- provided
-
-
- org.springframework.boot
- spring-boot-starter
- ${spring.boot.version}
-
-
- org.apache.logging.log4j
- log4j-to-slf4j
-
-
-
-
- org.springframework.boot
- spring-boot-starter-data-jpa
- ${spring.boot.version}
-
-
- org.hibernate
- hibernate-entitymanager
-
-
- org.hibernate
- hibernate-core
-
-
- org.springframework.boot
- spring-boot-starter-logging
-
-
- javax.xml.bind
- jaxb-api
-
-
-
-
- org.springframework.boot
- spring-boot-starter-test
- ${spring.boot.version}
-
-
- org.eclipse.persistence
- org.eclipse.persistence.jpa
- ${eclipselink.version}
-
-
- org.springframework.plugin
- spring-plugin-core
- ${spring.plugin.core.version}
-
+
+
+ org.springframework.cloud
+ spring-cloud-dependencies
+ ${spring.cloud.version}
+ pom
+ import
+
+
+ org.springframework.boot
+ spring-boot-starter-web
+ ${spring.boot.version}
+
+
+ com.fasterxml.jackson.datatype
+ jackson-datatype-jdk8
+
+
+ com.fasterxml.jackson.datatype
+ jackson-datatype-jsr310
+
+
+ com.fasterxml.jackson.module
+ jackson-module-parameter-names
+
+
+
+
+ org.springframework.boot
+ spring-boot-starter-tomcat
+ ${spring.boot.version}
+ provided
+
+
+ org.springframework.boot
+ spring-boot-starter
+ ${spring.boot.version}
+
+
+ org.apache.logging.log4j
+ log4j-to-slf4j
+
+
+
+
+ org.springframework.boot
+ spring-boot-starter-data-jpa
+ ${spring.boot.version}
+
+
+ org.hibernate
+ hibernate-entitymanager
+
+
+ org.hibernate
+ hibernate-core
+
+
+ org.springframework.boot
+ spring-boot-starter-logging
+
+
+ javax.xml.bind
+ jaxb-api
+
+
+
+
+ org.springframework.boot
+ spring-boot-starter-test
+ ${spring.boot.version}
+
+
+ org.eclipse.persistence
+ org.eclipse.persistence.jpa
+ ${eclipselink.version}
+
+
+ org.springframework.plugin
+ spring-plugin-core
+ ${spring.plugin.core.version}
+
-
- org.springdoc
- springdoc-openapi-starter-webmvc-ui
- ${springdoc-openapi.version}
-
+
+ org.springdoc
+ springdoc-openapi-starter-webmvc-ui
+ ${springdoc-openapi.version}
+
-
-
- io.protostuff
- protostuff-core
- ${io-protostuff.version}
-
-
- io.protostuff
- protostuff-runtime
- ${io-protostuff.version}
-
+
+
+ io.protostuff
+ protostuff-core
+ ${io-protostuff.version}
+
+
+ io.protostuff
+ protostuff-runtime
+ ${io-protostuff.version}
+
-
-
- cz.jirutka.rsql
- rsql-parser
- ${rsql-parser.version}
-
-
- commons-io
- commons-io
- ${commons-io.version}
-
-
- org.apache.commons
- commons-collections4
- ${commons-collections4.version}
-
+
+
+ cz.jirutka.rsql
+ rsql-parser
+ ${rsql-parser.version}
+
+
+ commons-io
+ commons-io
+ ${commons-io.version}
+
+
+ org.apache.commons
+ commons-collections4
+ ${commons-collections4.version}
+
-
-
- io.github.classgraph
- classgraph
- ${classgraph.version}
- test
-
-
- org.springframework.amqp
- spring-rabbit-junit
- ${spring-amqp.version}
- test
-
-
- org.springframework.amqp
- spring-rabbit-test
- ${spring-amqp.version}
- test
-
-
- io.qameta.allure
- allure-junit5
- ${allure.version}
- test
-
-
- org.awaitility
- awaitility
- ${awaitility.version}
-
-
-
+
+
+ io.github.classgraph
+ classgraph
+ ${classgraph.version}
+ test
+
+
+ org.springframework.amqp
+ spring-rabbit-junit
+ ${spring-amqp.version}
+ test
+
+
+ org.springframework.amqp
+ spring-rabbit-test
+ ${spring-amqp.version}
+ test
+
+
+ io.qameta.allure
+ allure-junit5
+ ${allure.version}
+ test
+
+
+ org.awaitility
+ awaitility
+ ${awaitility.version}
+
+
+
-
-
- org.projectlombok
- lombok
- true
-
-
+
+
+ org.projectlombok
+ lombok
+ true
+
+
diff --git a/site/README.md b/site/README.md
index 21dda6a65..7585152ed 100644
--- a/site/README.md
+++ b/site/README.md
@@ -1,15 +1,22 @@
# Eclipse hawkBit Documentation
-The hawkBit documentation is built with [Hugo](https://www.gohugo.io/) using the [Material](http://github.com/digitalcraftsman/hugo-material-docs)
+
+The hawkBit documentation is built with [Hugo](https://www.gohugo.io/) using
+the [Material](http://github.com/digitalcraftsman/hugo-material-docs)
theme. Compiling the documentation is not included within the regular Maven build.
## Prerequisites
-1. **Install Hugo**: see [installing Hugo](https://gohugo.io/getting-started/installing/) documentation on how to install Hugo.
-2. **Install NODE.js and npm** see [installing Node.js and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) documentation on how to install Node.js and npm
-3. **Install Redocly CLI** see [installing Redocly CLI](https://redocly.com/docs/cli/installation/) documentation on how to install Redocly CLI
+
+1. **Install Hugo**: see [installing Hugo](https://gohugo.io/getting-started/installing/) documentation on how to
+ install Hugo.
+2. **Install NODE.js and npm**
+ see [installing Node.js and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) documentation on
+ how to install Node.js and npm
+3. **Install Redocly CLI** see [installing Redocly CLI](https://redocly.com/docs/cli/installation/) documentation on how
+ to install Redocly CLI
4. **Install hawkBit**: run `mvn install` in the parent directory to generate the latest REST docs for hawkBit.
-
## Build and Serve documentation
+
The following Maven targets are available in order to build and serve the documentation:
* `mvn install`: _i._ Copies the generated REST docs to `content/rest-api/` and _ii._ downloads the required Hugo theme
@@ -19,6 +26,7 @@ The following Maven targets are available in order to build and serve the docume
* `mvn clean`: Delete generated artifacts (REST docs, Hugo theme)
## Generate /public folder
+
In order to generate the `/public` folder, which can be put on a web-server, run the following command:
```bash
diff --git a/site/config.toml b/site/config.toml
index 8b7303789..c7b693e14 100755
--- a/site/config.toml
+++ b/site/config.toml
@@ -16,95 +16,95 @@ metadataformat = "toml"
canonifyurls = false
[markup]
- [markup.goldmark]
- [markup.goldmark.extensions]
- typographer = true
- [markup.goldmark.renderer]
- unsafe = true
+[markup.goldmark]
+[markup.goldmark.extensions]
+typographer = true
+[markup.goldmark.renderer]
+unsafe = true
[markup.highlight]
- codeFences = false
+codeFences = false
[params]
- # General information
- author = "The Eclipse hawkBit Project"
- description = "IoT. Update. Device."
- copyright = "The Eclipse hawkBit Project"
- logo = "images/hawkbit_icon.png"
- favicon = "images/favicon.ico"
+# General information
+author = "The Eclipse hawkBit Project"
+description = "IoT. Update. Device."
+copyright = "The Eclipse hawkBit Project"
+logo = "images/hawkbit_icon.png"
+favicon = "images/favicon.ico"
- # Repository
- provider = "GitHub"
- repo_url = "https://github.com/eclipse-hawkbit/hawkbit"
+# Repository
+provider = "GitHub"
+repo_url = "https://github.com/eclipse-hawkbit/hawkbit"
- permalink = "#"
+permalink = "#"
- # Custom assets
- custom_css = ["css/hawkbit.css","//www.eclipse.org/eclipse.org-common/themes/solstice/public/stylesheets/vendor/cookieconsent/cookieconsent.min.css"]
- custom_js = []
+# Custom assets
+custom_css = ["css/hawkbit.css", "//www.eclipse.org/eclipse.org-common/themes/solstice/public/stylesheets/vendor/cookieconsent/cookieconsent.min.css"]
+custom_js = []
- # Syntax highlighting theme
- highlight_css = ""
+# Syntax highlighting theme
+highlight_css = ""
[params.palette]
- primary = "deep-purple"
- accent = "light-green"
+primary = "deep-purple"
+accent = "light-green"
[params.font]
- text = "Ubuntu"
- code = "Ubuntu Mono"
+text = "Ubuntu"
+code = "Ubuntu Mono"
[social]
- github = "eclipse/hawkbit"
- gitter = "eclipse/hawkbit"
- docker = "hawkbit"
+github = "eclipse/hawkbit"
+gitter = "eclipse/hawkbit"
+docker = "hawkbit"
[[menu.main]]
- name = "What is hawkBit"
- url = "/whatishawkbit/"
- weight = 10
+name = "What is hawkBit"
+url = "/whatishawkbit/"
+weight = 10
[[menu.main]]
- name = "Getting started"
- url = "/gettingstarted/"
- weight = 20
+name = "Getting started"
+url = "/gettingstarted/"
+weight = 20
[[menu.main]]
- name = "Guides"
- url = "/guides/"
- weight = 30
+name = "Guides"
+url = "/guides/"
+weight = 30
[[menu.main]]
- name = "Features"
- url = "/features/"
- weight = 40
+name = "Features"
+url = "/features/"
+weight = 40
[[menu.main]]
- name = "Concepts"
- url = "/concepts/"
- weight = 50
+name = "Concepts"
+url = "/concepts/"
+weight = 50
[[menu.main]]
- name = "Architecture"
- url = "/architecture/"
- weight = 60
+name = "Architecture"
+url = "/architecture/"
+weight = 60
[[menu.main]]
- name = "APIs"
- url = "/apis/"
- weight = 80
+name = "APIs"
+url = "/apis/"
+weight = 80
[[menu.main]]
- name = "Release notes"
- url = "/release-notes/"
- weight = 90
+name = "Release notes"
+url = "/release-notes/"
+weight = 90
[[menu.main]]
- name = "Blog"
- url = "/blog/"
- weight = 100
+name = "Blog"
+url = "/blog/"
+weight = 100
[[menu.main]]
- name = "Community"
- url = "/community/"
- weight = 110
+name = "Community"
+url = "/community/"
+weight = 110
diff --git a/site/content/apis/ddi_api.md b/site/content/apis/ddi_api.md
index 2865c76da..5037b7047 100644
--- a/site/content/apis/ddi_api.md
+++ b/site/content/apis/ddi_api.md
@@ -4,32 +4,39 @@ parent: APIs
weight: 82
---
-The hawkBit [update server](https://github.com/eclipse-hawkbit/hawkbit) provides REST resources which are consumed by the device to retrieve software update tasks.
+The hawkBit [update server](https://github.com/eclipse-hawkbit/hawkbit) provides REST resources which are consumed by
+the device to retrieve software update tasks.
This API is based on HTTP standards and a polling mechanism.
{{% note %}}
-In DDI the target is identified using a **controllerId**. Controller is used as a term for the actual service/client on the device. That allows users to have in some cases even multiple clients on the same target for different tasks, e.g. Firmware update and App management.
+In DDI the target is identified using a **controllerId**. Controller is used as a term for the actual service/client on
+the device. That allows users to have in some cases even multiple clients on the same target for different tasks, e.g.
+Firmware update and App management.
{{% /note %}}
## State Machine Mapping
-For historical reasons the DDI has a different state machine and status messages than the [Target State Machine](../../concepts/targetstate/) of the hawkBit update server.
+For historical reasons the DDI has a different state machine and status messages than
+the [Target State Machine](../../concepts/targetstate/) of the hawkBit update server.
-This is kept in order to ensure that _DDI_ stays compatible for devices out there in the field. A future version "2" of _DDI_ might change that. _DDI_ also defines more states than the update server, e.g. multiple DDI states are currently mapped by the _DDI_ implementation to _RUNNING_ state. It is possible that in the future hawkBit will fully leverage these additional states.
+This is kept in order to ensure that _DDI_ stays compatible for devices out there in the field. A future version "2" of
+_DDI_ might change that. _DDI_ also defines more states than the update server, e.g. multiple DDI states are currently
+mapped by the _DDI_ implementation to _RUNNING_ state. It is possible that in the future hawkBit will fully leverage
+these additional states.
The _DDI_ API allows the device to provide the following feedback messages:
-DDI `status.execution` type | handling by update server | Mapped ActionStatus type
---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -----------------------------------------------------
-CANCELED | This is send by the target as confirmation of a cancellation request by the update server. | CANCELED
-REJECTED | This is send by the target in case an update of a cancellation is rejected, i.e. cannot be fulfilled at this point in time. Note: the target should send a CLOSED->ERROR if it believes it will not be able to proceed the action at all. | WARNING
-CLOSED | Target completes the action either with `status.result.finished` SUCCESS or FAILURE as result. Note: DDI defines also a status NONE which will not be interpreted by the update server and handled like SUCCESS. | ERROR (DDI FAILURE) or FINISHED (DDI SUCCESS or NONE)
-DOWNLOAD | This can be used by the target to inform that it is downloading artifacts of the action. | DOWNLOAD
-DOWNLOADED | This can be used by the target to inform that it has downloaded artifacts of the action. | DOWNLOADED
-PROCEEDING | This can be used by the target to inform that it is working on the action. | RUNNING
-SCHEDULED | This can be used by the target to inform that it scheduled on the action. | RUNNING
-RESUMED | This can be used by the target to inform that it continued to work on the action. | RUNNING
+ DDI `status.execution` type | handling by update server | Mapped ActionStatus type
+-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------
+ CANCELED | This is send by the target as confirmation of a cancellation request by the update server. | CANCELED
+ REJECTED | This is send by the target in case an update of a cancellation is rejected, i.e. cannot be fulfilled at this point in time. Note: the target should send a CLOSED->ERROR if it believes it will not be able to proceed the action at all. | WARNING
+ CLOSED | Target completes the action either with `status.result.finished` SUCCESS or FAILURE as result. Note: DDI defines also a status NONE which will not be interpreted by the update server and handled like SUCCESS. | ERROR (DDI FAILURE) or FINISHED (DDI SUCCESS or NONE)
+ DOWNLOAD | This can be used by the target to inform that it is downloading artifacts of the action. | DOWNLOAD
+ DOWNLOADED | This can be used by the target to inform that it has downloaded artifacts of the action. | DOWNLOADED
+ PROCEEDING | This can be used by the target to inform that it is working on the action. | RUNNING
+ SCHEDULED | This can be used by the target to inform that it scheduled on the action. | RUNNING
+ RESUMED | This can be used by the target to inform that it continued to work on the action. | RUNNING
## DDI APIs
diff --git a/site/content/apis/dmf_api.md b/site/content/apis/dmf_api.md
index 3c4d4ccf8..3237d2862 100644
--- a/site/content/apis/dmf_api.md
+++ b/site/content/apis/dmf_api.md
@@ -4,7 +4,8 @@ parent: API
weight: 83
---
-The DMF API provides Java classes which allows that the message body can be deserialized at runtime into a Java object. Also Java classes can be used to serialize Java objects into JSON bodies to send a message to hawkBit.
+The DMF API provides Java classes which allows that the message body can be deserialized at runtime into a Java object.
+Also Java classes can be used to serialize Java objects into JSON bodies to send a message to hawkBit.
Currently, bodies of messages are based on JSON.
@@ -22,20 +23,22 @@ Bindings determine how messages get put in this place
Queues can also be bound to multiple exchanges.
**Exchanges** are just publish messages.
-The user decides who can produce on an exchange and who can create bindings on that exchange for delivery to a specific queue.
+The user decides who can produce on an exchange and who can create bindings on that exchange for delivery to a specific
+queue.
hawkBit will create all necessary queues, exchanges and bindings for the user, making it easy to get started.
The exchange name for outgoing messages is **dmf.exchange**.
-The user has to set a `reply_to` header (see chapter below), in order to specify the exchange to which hawkBit should reply to.
+The user has to set a `reply_to` header (see chapter below), in order to specify the exchange to which hawkBit should
+reply to.
The following chapter describes the message body, header and properties.
-Note: the DMF protocol was intended to be compatible to other use cases by design. As a result, DMF uses the term **thing** and not **target** but they are actually synonyms in this case.
+Note: the DMF protocol was intended to be compatible to other use cases by design. As a result, DMF uses the term *
+*thing** and not **target** but they are actually synonyms in this case.
## Messages sent to hawkBit (Client -> hawkBit)
-
### THING_CREATED
Message to register and update a provisioning target.
@@ -76,9 +79,10 @@ Payload Template (optional):
The "name" property specifies the name of the thing, which by default is the thing ID. This property is optional.
-The "type" property specifies name of a target type which should be assigned to the created/updated target. The
+The "type" property specifies name of a target type which should be assigned to the created/updated target. The
target type with the specified name should be created in advance, otherwise it can't be assigned to the target,
resulting in:
+
* error is logged
* if the target does not exist then it is created without any target type assigned
* if it exists already then no changes to its target type assignment are made.
@@ -87,8 +91,8 @@ If the "type" property is set to a blank string while updating an existing targe
assignment is removed from the target. This property is optional and if omitted then no changes to the target type
assignment are made.
-The "attributeUpdate" property provides the attributes of the thing, for details see UPDATE_ATTRIBUTES message. This property is optional.
-
+The "attributeUpdate" property provides the attributes of the thing, for details see UPDATE_ATTRIBUTES message. This
+property is optional.
### THING_REMOVED
@@ -112,7 +116,8 @@ Example headers
### UPDATE_ATTRIBUTES
-Message to update target attributes. This message can be send in response to a REQUEST_ATTRIBUTES_UPDATE event, sent by hawkBit.
+Message to update target attributes. This message can be send in response to a REQUEST_ATTRIBUTES_UPDATE event, sent by
+hawkBit.
| Header | Description | Type | Mandatory |
|---------|----------------------------------|----------------------------------|-----------|
@@ -121,9 +126,9 @@ Message to update target attributes. This message can be send in response to a R
| thingId | The ID of the registered thing | String | true |
| tenant | The tenant this thing belongs to | String | false |
-| Message Properties | Description | Type | Mandatory |
-|-----------------------------|----------------------------------|--------|-----------|
-| content_type | The content type of the payload | String | true |
+| Message Properties | Description | Type | Mandatory |
+|--------------------|---------------------------------|--------|-----------|
+| content_type | The content type of the payload | String | true |
Example header and payload:
@@ -143,7 +148,9 @@ Payload Template:
}
```
-The "mode" property specifies the update mode that should be applied. This property is optional. Possible [mode](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfUpdateMode.java) values:
+The "mode" property specifies the update mode that should be applied. This property is optional.
+Possible [mode](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfUpdateMode.java)
+values:
| Value | Description |
|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -165,7 +172,8 @@ Message to send an action status event to hawkBit.
|--------------------|---------------------------------|--------|-----------|
| content_type | The content type of the payload | String | true |
-Payload Template (the Java representation is [ActionUpdateStatus](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfActionUpdateStatus.java)):
+Payload Template (the Java representation
+is [ActionUpdateStatus](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfActionUpdateStatus.java)):
```json
{
@@ -176,7 +184,8 @@ Payload Template (the Java representation is [ActionUpdateStatus](https://github
}
```
-Possible [actionStatus](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfActionStatus.java) values:
+Possible [actionStatus](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfActionStatus.java)
+values:
| Value | Description |
|-----------------|-----------------------------------------|
@@ -207,7 +216,8 @@ Example header and payload:
### PING
-hawkBit allows DMF clients to check the availability of the DMF service. For this scenario DMF specifies a PING message that can be sent by the client:
+hawkBit allows DMF clients to check the availability of the DMF service. For this scenario DMF specifies a PING message
+that can be sent by the client:
| Header | Description | Type | Mandatory |
|--------|--------------------------------|---------------------|-----------|
@@ -255,7 +265,8 @@ Example Headers and Payload:
}
```
-After sending this message, an action status event with either actionStatus=CANCELED or actionStatus=CANCEL_REJECTED has to be returned.
+After sending this message, an action status event with either actionStatus=CANCELED or actionStatus=CANCEL_REJECTED has
+to be returned.
Example header and payload when cancellation is successful:
@@ -287,10 +298,10 @@ Example header and payload when cancellation is rejected:
}
```
-
### DOWNLOAD_AND_INSTALL or DOWNLOAD
-Message sent by hawkBit to initialize an update or download task. Note: in case of a maintenance window configured but not yet active the message will have the topic _DOWNLOAD_ instead of _DOWNLOAD_AND_INSTALL_.
+Message sent by hawkBit to initialize an update or download task. Note: in case of a maintenance window configured but
+not yet active the message will have the topic _DOWNLOAD_ instead of _DOWNLOAD_AND_INSTALL_.
| Header | Description | Type | Mandatory |
|---------|------------------------------------------------|---------------------------------------------------|-----------|
@@ -303,7 +314,8 @@ Message sent by hawkBit to initialize an update or download task. Note: in case
|--------------------|---------------------------------|--------|-----------|
| content_type | The content type of the payload | String | true |
-Payload Template (the Java representation is [DmfDownloadAndUpdateRequest](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfDownloadAndUpdateRequest.java)):
+Payload Template (the Java representation
+is [DmfDownloadAndUpdateRequest](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfDownloadAndUpdateRequest.java)):
```json
{
@@ -375,13 +387,13 @@ Example header and payload:
}
```
-
### MULTI_ACTION
-If `multi.assignments.enabled` is enabled, this message is sent instead of DOWNLOAD_AND_INSTALL, DOWNLOAD, or CANCEL_DOWNLOAD
- by hawkBit to initialize update, download, or cancel task(s).
+If `multi.assignments.enabled` is enabled, this message is sent instead of DOWNLOAD_AND_INSTALL, DOWNLOAD, or
+CANCEL_DOWNLOAD
+by hawkBit to initialize update, download, or cancel task(s).
- With weight, one can set the priority to the action. The higher the weight, the higher is the priority of an action.
+With weight, one can set the priority to the action. The higher the weight, the higher is the priority of an action.
| Header | Description | Type | Mandatory |
|---------|------------------------------------------------|-----------------------------|-----------|
@@ -394,7 +406,8 @@ If `multi.assignments.enabled` is enabled, this message is sent instead of DOWNL
|--------------------|---------------------------------|--------|-----------|
| content_type | The content type of the payload | String | true |
-Payload Template (the Java representation is [DmfMultiActionRequest](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfMultiActionRequest.java)):
+Payload Template (the Java representation
+is [DmfMultiActionRequest](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-dmf/hawkbit-dmf-api/src/main/java/org/eclipse/hawkbit/dmf/json/model/DmfMultiActionRequest.java)):
```json
[{
@@ -540,7 +553,6 @@ Example header and payload:
}]
```
-
### THING_DELETED
Message sent by hawkBit when a target has been deleted.
@@ -557,7 +569,6 @@ Example header:
|--------------------------------------------------------------|-------------------|
| type=THING\_DELETED tenant=default thingId=abc | |
-
### REQUEST_ATTRIBUTES_UPDATE
Message sent by Eclipse hawkBit when a re-transmission of target attributes is requested.
@@ -575,10 +586,10 @@ Example headers:
|----------------------------------------------------------------------------------------------|-------------------|
| type=EVENT tenant=default thingId=abc topic=REQUEST\_ATTRIBUTES\_UPDATE | |
-
### PING_RESPONSE
-_hawkBit_ will respond to the PING message with a PING_RESPONSE type message that has the same correlationId as the original PING message:
+_hawkBit_ will respond to the PING message with a PING_RESPONSE type message that has the same correlationId as the
+original PING message:
| Header | Description | Type | Mandatory |
|--------|--------------------------------|------------------------------|-----------|
@@ -590,7 +601,8 @@ _hawkBit_ will respond to the PING message with a PING_RESPONSE type message tha
| correlationId | CorrelationId of the original PING request | String | true |
| content_type | The content type of the payload | String | true |
-The PING_RESPONSE also contains a timestamp (i.e. the difference, measured in milliseconds, between the current time and midnight, January 1, 1970 UTC) as plain text. It is not guaranteed that this timestamp is completely accurate.
+The PING_RESPONSE also contains a timestamp (i.e. the difference, measured in milliseconds, between the current time and
+midnight, January 1, 1970 UTC) as plain text. It is not guaranteed that this timestamp is completely accurate.
| Header | MessageProperties |
|-------------------------------------------|-------------------------|
diff --git a/site/content/apis/management_api.md b/site/content/apis/management_api.md
index 5070b504c..cf0751778 100644
--- a/site/content/apis/management_api.md
+++ b/site/content/apis/management_api.md
@@ -4,16 +4,20 @@ parent: API
weight: 81
---
-The Management API is a RESTful API that enables to perform Create/Read/Update/Delete operations for provisioning targets (i.e. devices) and repository content (i.e. software).
+The Management API is a RESTful API that enables to perform Create/Read/Update/Delete operations for provisioning
+targets (i.e. devices) and repository content (i.e. software).
-Based on the Management API you can manage and monitor software update operations via HTTP/HTTPS. The _Management API_ supports JSON payload with hypermedia as well as filtering, sorting and paging. Furthermore the Management API provides permission based access control and standard roles as well as custom role creation.
+Based on the Management API you can manage and monitor software update operations via HTTP/HTTPS. The _Management API_
+supports JSON payload with hypermedia as well as filtering, sorting and paging. Furthermore the Management API provides
+permission based access control and standard roles as well as custom role creation.
The API is protected and needs authentication and authorization based on the security concept.
## API Version
-hawkBit provides an consistent Management API interface that guarantees backwards compatibility for future releases by version control.
+hawkBit provides an consistent Management API interface that guarantees backwards compatibility for future releases by
+version control.
The current version of the Management API is `version 1 (v1)` with the URI http://localhost:8080/rest/v1/
@@ -42,10 +46,11 @@ In addition, for POST and PUT requests the `Content-Type` header has to be set.
## Request Body
-Besides the relevant data (name, description, createdBy etc.) of a resource entity, a resource entity also has URIs (`_links`) to linked resource entities.
-
-A _Distribution Set_ entity may have for example URIs to artifacts, _Software Modules_, _Software Module Types_ and metadata.
+Besides the relevant data (name, description, createdBy etc.) of a resource entity, a resource entity also has
+URIs (`_links`) to linked resource entities.
+A _Distribution Set_ entity may have for example URIs to artifacts, _Software Modules_, _Software Module Types_ and
+metadata.
```json
"_links": {
@@ -65,5 +70,4 @@ A _Distribution Set_ entity may have for example URIs to artifacts, _Software Mo
## Management APIs
-
diff --git a/site/content/blog/2018-07-26-first-release.md b/site/content/blog/2018-07-26-first-release.md
index 726d75ad1..507568836 100644
--- a/site/content/blog/2018-07-26-first-release.md
+++ b/site/content/blog/2018-07-26-first-release.md
@@ -4,17 +4,19 @@ parent: Blog
weight: 200
---
-hawkBit is a domain-independent back-end framework for rolling out software updates to constrained edge devices as well
-as more powerful controllers and gateways connected to IP based networking infrastructure. It is part of the Eclipse IoT
+hawkBit is a domain-independent back-end framework for rolling out software updates to constrained edge devices as well
+as more powerful controllers and gateways connected to IP based networking infrastructure. It is part of the Eclipse IoT
since 2015 and with version _0.2.0_ a first release is available.
-In this article, we want to give an overview of the latest highlights of hawkBit and let you know how you can get
+In this article, we want to give an overview of the latest highlights of hawkBit and let you know how you can get
started in seconds.
-## Finally, it is here!
+## Finally, it is here!
-After being around in the Eclipse IoT realm for quite some time now, we are more than happy to announce our first release:
-[_Eclipse hawkBit 0.2.0_](https://projects.eclipse.org/projects/iot.hawkbit/releases/0.2.0). The release can be found on [Maven Central](https://mvnrepository.com/artifact/org.eclipse.hawkbit)
+After being around in the Eclipse IoT realm for quite some time now, we are more than happy to announce our first
+release:
+[_Eclipse hawkBit 0.2.0_](https://projects.eclipse.org/projects/iot.hawkbit/releases/0.2.0). The release can be found
+on [Maven Central](https://mvnrepository.com/artifact/org.eclipse.hawkbit)
and [Docker Hub](https://hub.docker.com/r/hawkbit/hawkbit-update-server/). It includes the following core features:
* Device and Software Repository
@@ -31,63 +33,69 @@ The features are accessible via the following interfaces:

-
## What's new?
-Whenever there is a new release, the first question that comes to mind is: What's new? Since this is our first release,
-one could argue that everything is new. However, most of the features are already well-established. This holds true, for
-example, for our APIs or the Rollout Management. Nevertheless, there have been some recent updates to hawkBit, which we
-do not want to leave unmentioned:
+Whenever there is a new release, the first question that comes to mind is: What's new? Since this is our first release,
+one could argue that everything is new. However, most of the features are already well-established. This holds true, for
+example, for our APIs or the Rollout Management. Nevertheless, there have been some recent updates to hawkBit, which we
+do not want to leave unmentioned:
### Streamlined UI
-The probably most noticeable change has been the removal of the two buttons (`Drop here to delete` and `Actions`) at the
-bottom of the _Deployment_, _Distributions_, and _Upload_ view. This is a major usability improvement! For example,
-deleting an item required (1) dragging an item onto the delete button, (2) opening the delete pop-up, and (3) confirming
-the deletion. Now, an item can be easily removed by clicking on its remove icon and confirming the action. Moreover,
-multiple (or all `CTRL` + `A`) items can be selected and removed at once using the same mechanism. This is not only
-faster and more intuitive, it also saves a lot of display real estate which can now be used to focus on what is important.
+The probably most noticeable change has been the removal of the two buttons (`Drop here to delete` and `Actions`) at the
+bottom of the _Deployment_, _Distributions_, and _Upload_ view. This is a major usability improvement! For example,
+deleting an item required (1) dragging an item onto the delete button, (2) opening the delete pop-up, and (3) confirming
+the deletion. Now, an item can be easily removed by clicking on its remove icon and confirming the action. Moreover,
+multiple (or all `CTRL` + `A`) items can be selected and removed at once using the same mechanism. This is not only
+faster and more intuitive, it also saves a lot of display real estate which can now be used to focus on what is
+important.
We hope you like this change as much as we do! _(Requires: hawkBit > 0.2.2)_

### MS SQL Server
-Eclipse hawkBit supports a range of different SQL databases. Up to now, these have been the internal H2 database (which can be
-used for testing, development, or trial) and MySQL/MariaDB for production-grade usage. This list is now extended by
+Eclipse hawkBit supports a range of different SQL databases. Up to now, these have been the internal H2 database (which
+can be
+used for testing, development, or trial) and MySQL/MariaDB for production-grade usage. This list is now extended by
Microsoft's SQL Server which is also available in production grade, as well as, IBM's DB2 for testing and development.
### Open Sourced REST docs
-A huge benefit for the community is the recently open sourced REST docs of hawkBit. This has been an [open request](https://github.com/eclipse-hawkbit/hawkbit/issues/480)
-for some time, which we were happy to meet. The documentation is generated using [Spring REST docs](https://spring.io/projects/spring-restdocs), based on unit-tests. These tests, with the respective documentation, are now available in the [code base](https://github.com/eclipse-hawkbit/hawkbit/pull/688).
- Furthermore, the API documentation will be hosted on our new [website](https://www.eclipse.org/hawkbit/) (coming soon).
-
+A huge benefit for the community is the recently open sourced REST docs of hawkBit. This has been
+an [open request](https://github.com/eclipse-hawkbit/hawkbit/issues/480)
+for some time, which we were happy to meet. The documentation is generated
+using [Spring REST docs](https://spring.io/projects/spring-restdocs), based on unit-tests. These tests, with the
+respective documentation, are now available in the [code base](https://github.com/eclipse-hawkbit/hawkbit/pull/688).
+Furthermore, the API documentation will be hosted on our new [website](https://www.eclipse.org/hawkbit/) (coming soon).
### Docker Images
-In order to enable interested parties to get started with hawkBit conveniently, we decided to provide the
-[Update Server as a Docker image](https://hub.docker.com/r/hawkbit/hawkbit-update-server/) on Docker Hub. The image comes
-in two flavors: The default image uses the internal H2 database, while the images with a `-mysql` suffix contain the MySQL
-driver to allow connecting a MySQL database. In addition to the Docker image, the hawkBit repository contains a
-[docker-compose.yml](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-runtime/hawkbit-update-server/docker/docker-compose.yml)
-that not only starts the Update Server, but further includes a MySQL database and a RabbitMQ message broker so you're
-able to use Device Management Federation (DMF) as well.
+In order to enable interested parties to get started with hawkBit conveniently, we decided to provide the
+[Update Server as a Docker image](https://hub.docker.com/r/hawkbit/hawkbit-update-server/) on Docker Hub. The image
+comes
+in two flavors: The default image uses the internal H2 database, while the images with a `-mysql` suffix contain the
+MySQL
+driver to allow connecting a MySQL database. In addition to the Docker image, the hawkBit repository contains a
+[docker-compose.yml](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-runtime/hawkbit-update-server/docker/docker-compose.yml)
+that not only starts the Update Server, but further includes a MySQL database and a RabbitMQ message broker so you're
+able to use Device Management Federation (DMF) as well.
-To start the hawkBit Update Server image, open a terminal and run:
+To start the hawkBit Update Server image, open a terminal and run:
```
$ docker run -d -p 8080:8080 hawkbit/hawkbit-update-server
```
+
{{% note %}}
_Note: This requires a running [Docker deamon](https://docs.docker.com/install/) on your system._
{{% /note %}}
-Now, browse to [http://localhost:8080](http://localhost:8080) and log-in with `admin:admin`. There you go!
+Now, browse to [http://localhost:8080](http://localhost:8080) and log-in with `admin:admin`. There you go!
## Community Updates
-Although features and functionality play a major role in the hawkBit project, there is also some interesting news from
+Although features and functionality play a major role in the hawkBit project, there is also some interesting news from
the community. As of July 2018, there have been:
* Pull Requests: 587
@@ -98,17 +106,19 @@ the community. As of July 2018, there have been:
### New Project Lead and Committers
-We are happy to announce that the hawkBit project got a new project lead. In addition to
-[Kai Zimmermann](https://projects.eclipse.org/user/6364), project lead from the first hour,
-[Jeroen Laverman](https://projects.eclipse.org/user/10982) joined the lead to support him in this responsibility.
-Moreover, with [Stefan Behl](https://projects.eclipse.org/user/10842) and Jeroen Laverman, two new committers are aboard.
-
+We are happy to announce that the hawkBit project got a new project lead. In addition to
+[Kai Zimmermann](https://projects.eclipse.org/user/6364), project lead from the first hour,
+[Jeroen Laverman](https://projects.eclipse.org/user/10982) joined the lead to support him in this responsibility.
+Moreover, with [Stefan Behl](https://projects.eclipse.org/user/10842) and Jeroen Laverman, two new committers are
+aboard.
## What's next?
-Looking ahead, there are two major topics that we want to tackle next: First, there is the migration of our UI from Vaadin
+Looking ahead, there are two major topics that we want to tackle next: First, there is the migration of our UI from
+Vaadin
7 to Vaadin 8, since Vaadin announced the end-of-life for our current version. Another big topic will be the update
-to Spring Boot 2. On the community side, we are in the final stage of updating our [website](https://www.eclipse.org/hawkbit/)
-with a new design, so make sure you stop by in a couple of days to check it out. Finally, the hawkBit team will be
+to Spring Boot 2. On the community side, we are in the final stage of updating
+our [website](https://www.eclipse.org/hawkbit/)
+with a new design, so make sure you stop by in a couple of days to check it out. Finally, the hawkBit team will be
present at EclipseCon Europe 2018, so if you are interested in meeting us, that is the place to be.
diff --git a/site/content/blog/2023-09-21-epl2.0.md b/site/content/blog/2023-09-21-epl2.0.md
index fbba6a511..fce631504 100644
--- a/site/content/blog/2023-09-21-epl2.0.md
+++ b/site/content/blog/2023-09-21-epl2.0.md
@@ -15,6 +15,7 @@ In this article, we want to give an overview of the latest highlights of hawkBit
Based on the issues
[Switch to EPL 2.0 License](https://github.com/eclipse-hawkbit/hawkbit/issues/1393) and
[Update hawkBit's license to EPL 2.0](https://github.com/eclipse-hawkbit/hawkbit/issues/1008)
-the hawkBit license is upgraded from [Eclipse Public License - Version 1.0](http://www.eclipse.org/org/documents/epl-v10.php) to
+the hawkBit license is upgraded
+from [Eclipse Public License - Version 1.0](http://www.eclipse.org/org/documents/epl-v10.php) to
[Eclipse Public License - v 2.0](https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt).
diff --git a/site/content/blog/2023-11-22-vaadin8_ui_discontinuation.md b/site/content/blog/2023-11-22-vaadin8_ui_discontinuation.md
index bdf811d84..f6784e201 100644
--- a/site/content/blog/2023-11-22-vaadin8_ui_discontinuation.md
+++ b/site/content/blog/2023-11-22-vaadin8_ui_discontinuation.md
@@ -8,18 +8,34 @@ In this article, we want to give an overview of the future of the hawkBit UI
## hawkBit Vaadin 8 UI discontinuation
-The hawkBit UI uses Vaadin as a web UI framework. It uses Vaadin 8 (8.14.3). This major version, according [Vaadin Roadmap](https://vaadin.com/roadmap), has no free support since 21st Feb 2022. There are some version releases after that date (8.15.0 - 8.16.0) that are Apache 2.0 licensed. However, since 8.16.1 ([see here](https://mvnrepository.com/artifact/com.vaadin/vaadin-server)) the license is [Commercial Vaadin Developer License 4.0](https://vaadin.com/license/cvdl-4.0), so they could not be used in hawkBit.
+The hawkBit UI uses Vaadin as a web UI framework. It uses Vaadin 8 (8.14.3). This major version,
+according [Vaadin Roadmap](https://vaadin.com/roadmap), has no free support since 21st Feb 2022. There are some version
+releases after that date (8.15.0 - 8.16.0) that are Apache 2.0 licensed. However, since
+8.16.1 ([see here](https://mvnrepository.com/artifact/com.vaadin/vaadin-server)) the license
+is [Commercial Vaadin Developer License 4.0](https://vaadin.com/license/cvdl-4.0), so they could not be used in hawkBit.
-We believe it is not a good practice to keep an out of free support library in an open source project like hawkBit. And moreover, even if we keep it, if a security vulnerability is discovered - all users shall opt for commercial support or to drop UI.
+We believe it is not a good practice to keep an out of free support library in an open source project like hawkBit. And
+moreover, even if we keep it, if a security vulnerability is discovered - all users shall opt for commercial support or
+to drop UI.
-There is another critical obstacle with keeping Vaadin 8 UI. At the moment hawkBit uses Spring Boot 2.7. According to [Spring Boot EOL](https://endoflife.date/spring-boot) Spring Boot 2.7 stream will reach end of support 24th Nov 2023. So, hawkBit shall be migrated to Spring Boot 3.0+. Since Vaadin 8 seem to be incompatible with Spring Boot 3 (they added support for Spring Boot 3 in Vaadin 24 ([Vaadin 24 pre release](https://vaadin.com/blog/vaadin-24-pre-release-available-for-spring-boot-3.0)) we shall drop Vaadin UI 8 anyway.
+There is another critical obstacle with keeping Vaadin 8 UI. At the moment hawkBit uses Spring Boot 2.7. According
+to [Spring Boot EOL](https://endoflife.date/spring-boot) Spring Boot 2.7 stream will reach end of support 24th Nov 2023.
+So, hawkBit shall be migrated to Spring Boot 3.0+. Since Vaadin 8 seem to be incompatible with Spring Boot 3 (they added
+support for Spring Boot 3 in Vaadin
+24 ([Vaadin 24 pre release](https://vaadin.com/blog/vaadin-24-pre-release-available-for-spring-boot-3.0)) we shall drop
+Vaadin UI 8 anyway.
-Many months ago we asked for community help to migrate hawkBit UI to newer Vaadin versions - [Urgent migration needed to a newer Vaadin version
-](https://github.com/eclipse-hawkbit/hawkbit/issues/1376) and gitter channel. However, there was no volunteer found to do the migration.
+Many months ago we asked for community help to migrate hawkBit UI to newer Vaadin
+versions - [Urgent migration needed to a newer Vaadin version
+](https://github.com/eclipse-hawkbit/hawkbit/issues/1376) and gitter channel. However, there was no volunteer found to
+do the migration.
-All this being said, unfortunately, we've come to the decision to drop the Vaadin 8 UI from the Eclipse hawkBit and the latest hawkBit release 0.3.0 is the last version of hawkBit that includes it. For the next 0.4.0 release we plan to remove this Vaadin 8 UI. Thus the hawkBit may become an UI-less project.
+All this being said, unfortunately, we've come to the decision to drop the Vaadin 8 UI from the Eclipse hawkBit and the
+latest hawkBit release 0.3.0 is the last version of hawkBit that includes it. For the next 0.4.0 release we plan to
+remove this Vaadin 8 UI. Thus the hawkBit may become an UI-less project.
+
+There were steps taken to mitigate the problem:
-There were steps taken to mitigate the problem:
* extending the REST API
* introducing Swagger UI which allow easier use of the REST API
diff --git a/site/content/blog/2024-01-16-0.4.1-release.md b/site/content/blog/2024-01-16-0.4.1-release.md
index 1e16634f2..005d4bd30 100644
--- a/site/content/blog/2024-01-16-0.4.1-release.md
+++ b/site/content/blog/2024-01-16-0.4.1-release.md
@@ -9,19 +9,42 @@ In this article, we want to give an overview of the 0.4.1 hawkBit release (Frida
## hawkBit [0.4.1](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.4.1) release
### Steps towards removal of the legacy Vaadin8-based UI
-As announced at [Vaadin 8 UI discontinuation](2023-11-22-vaadin8_ui_discontinuation.md) the current Vaadin 8 based UI will be removed. This release will likely be the last one including it. Some steps are taken to mitigate this.
-* First of all, this release introduces [Simple UI](https://github.com/eclipse-hawkbit/hawkbit/tree/0.4.1/hawkbit-runtime/hawkbit-simple-ui) - a demo/PoC level UI. It includes the most essential functionality allowing you to play around with hawkBit. It could not be compared to legacy UI in features and maturity in any case. Some notes for it:
+
+As announced at [Vaadin 8 UI discontinuation](2023-11-22-vaadin8_ui_discontinuation.md) the current Vaadin 8 based UI
+will be removed. This release will likely be the last one including it. Some steps are taken to mitigate this.
+
+* First of all, this release
+ introduces [Simple UI](https://github.com/eclipse-hawkbit/hawkbit/tree/0.4.1/hawkbit-runtime/hawkbit-simple-ui) - a
+ demo/PoC level UI. It includes the most essential functionality allowing you to play around with hawkBit. It could not
+ be compared to legacy UI in features and maturity in any case. Some notes for it:
* *Status* - as already said - low maturity and very feature-limited, *EXPERIMENTAL*
- * Intended for demo/play-around purposes. It could become an initial version of a new hawkBit UI but currently, there are no resources for further development. Any contribution to this UI in the direction of making it a full-fledged mature UI is welcome!
+ * Intended for demo/play-around purposes. It could become an initial version of a new hawkBit UI but currently,
+ there are no resources for further development. Any contribution to this UI in the direction of making it a
+ full-fledged mature UI is welcome!
* It provides features like - create software modules & distribution sets, targets, and rollouts
- * In contrast with legacy UI the new UI is a standalone application and uses only REST API to provide functionality to the user.
-* To the legacy monolith update server application there is added a new microservice-based application. As part of this effort, there was introduced an example of [legacy Vaadin 8 UI standalone application](https://github.com/eclipse-hawkbit/hawkbit/tree/0.4.1/hawkbit-runtime/hawkbit-vv8-ui). This legacy UI standalone application could be used together with future hawkBit update server versions as long as it is compatible and on the user's responsibility. Some notes for it:
- * *NOT RECOMMENDED* - it might contain security vulnerabilities and bugs. It could be hard to verify its compatibility with the new hawkBit versions.
- * *ON USER's RESPONSIBILITY* - no guarantees of any kind are provided for that application. It is entirely the user's responsibility to test, scan for vulnerabilities, and use it.
+ * In contrast with legacy UI the new UI is a standalone application and uses only REST API to provide functionality
+ to the user.
+* To the legacy monolith update server application there is added a new microservice-based application. As part of this
+ effort, there was introduced an example
+ of [legacy Vaadin 8 UI standalone application](https://github.com/eclipse-hawkbit/hawkbit/tree/0.4.1/hawkbit-runtime/hawkbit-vv8-ui).
+ This legacy UI standalone application could be used together with future hawkBit update server versions as long as it
+ is compatible and on the user's responsibility. Some notes for it:
+ * *NOT RECOMMENDED* - it might contain security vulnerabilities and bugs. It could be hard to verify its
+ compatibility with the new hawkBit versions.
+ * *ON USER's RESPONSIBILITY* - no guarantees of any kind are provided for that application. It is entirely the
+ user's responsibility to test, scan for vulnerabilities, and use it.
* Provides an option to use the legacy Vaadin 8 UI with the new hawkBit versions under the conditions above
* It uses directly the database and legacy update server code
* It includes the outdated Spring Boot 2.7 which is after its end of support
* It will not be developed any further and new features won't be available
* No bugfixes would be provided for it
+
### Extended access control management - entity-based
-There is a new feature implemented in access control management. Up until now, permissions (e.g. CREATE_TARGET) were assigned to the users, and based on that users were able to execute some action or not. Now there is added a pluggable mechanism via [AccessController](https://github.com/eclipse-hawkbit/hawkbit/blob/0.4.1/hawkbit-repository/hawkbit-repository-jpa/src/main/java/org/eclipse/hawkbit/repository/jpa/acm/AccessController.java) that allows to further restrict the access based on the entity. For instance, a developer could implement its custom access controller for targets that, depending on the user, could grant or reject permissions for accessing targets of certain target types.
\ No newline at end of file
+
+There is a new feature implemented in access control management. Up until now, permissions (e.g. CREATE_TARGET) were
+assigned to the users, and based on that users were able to execute some action or not. Now there is added a pluggable
+mechanism
+via [AccessController](https://github.com/eclipse-hawkbit/hawkbit/blob/0.4.1/hawkbit-repository/hawkbit-repository-jpa/src/main/java/org/eclipse/hawkbit/repository/jpa/acm/AccessController.java)
+that allows to further restrict the access based on the entity. For instance, a developer could implement its custom
+access controller for targets that, depending on the user, could grant or reject permissions for accessing targets of
+certain target types.
\ No newline at end of file
diff --git a/site/content/community.md b/site/content/community.md
index 41022e1bb..3d5fdfc72 100755
--- a/site/content/community.md
+++ b/site/content/community.md
@@ -5,41 +5,59 @@ weight: 90
## Presentations
-Here you can find links to arbitrary material covering Eclipse hawkBit which has been presented at events, conferences and meet-ups.
+Here you can find links to arbitrary material covering Eclipse hawkBit which has been presented at events, conferences
+and meet-ups.
-- 09/23/2015 - Eclipse IoT Working Group meeting - [slides](https://docs.bosch-iot-rollouts.com/slides/hawkBitProposal20150923.html)
+- 09/23/2015 - Eclipse IoT Working Group
+ meeting - [slides](https://docs.bosch-iot-rollouts.com/slides/hawkBitProposal20150923.html)
- 04/11/2015 - EclipseCon Europe 2015 - [slides](https://docs.bosch-iot-rollouts.com/slides/eclipseCon2015.html)
-- 03/09/2016 - EclipseCon North America 2016 - [slides](https://docs.bosch-iot-rollouts.com/slides/eclipseConNA2016.html)
-- 05/16/2016 - Eclipse Virtual IoT Meetup - [video](https://www.youtube.com/watch?v=g-dhKMaaanE) - [slides](https://docs.bosch-iot-rollouts.com/slides/virtualIoTMeetup2016.html)
-- 03/20/2017 - Eclipse IoT Day SanJose, CA - [video](https://www.youtube.com/watch?v=x5OfBgnYW44) - [slides](https://docs.bosch-iot-rollouts.com/slides/iotDaySanJose2017.pdf)
+- 03/09/2016 - EclipseCon North America
+ 2016 - [slides](https://docs.bosch-iot-rollouts.com/slides/eclipseConNA2016.html)
+- 05/16/2016 - Eclipse Virtual IoT
+ Meetup - [video](https://www.youtube.com/watch?v=g-dhKMaaanE) - [slides](https://docs.bosch-iot-rollouts.com/slides/virtualIoTMeetup2016.html)
+- 03/20/2017 - Eclipse IoT Day SanJose,
+ CA - [video](https://www.youtube.com/watch?v=x5OfBgnYW44) - [slides](https://docs.bosch-iot-rollouts.com/slides/iotDaySanJose2017.pdf)
- 09/12/2017 - Eclipse IoT Day ThingMonk 2017 - [video](https://www.youtube.com/watch?v=7hK-kiQjKGA)
-- 01/10/2018 - Eclipse Virtual IoT Meetup - [video](https://www.youtube.com/watch?v=8vcLXs9lc-4) - [slides](https://docs.bosch-iot-rollouts.com/slides/hawkBitIntroduction.html)
-- 10/22/2018 - Community Day EclipseCon Europe 2018 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2018.html)
-- 10/21/2019 - Community Day EclipseCon Europe 2019 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2019.html)
-- 10/19/2020 - Community Day EclipseCon Europe 2020 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2020.html)
+- 01/10/2018 - Eclipse Virtual IoT
+ Meetup - [video](https://www.youtube.com/watch?v=8vcLXs9lc-4) - [slides](https://docs.bosch-iot-rollouts.com/slides/hawkBitIntroduction.html)
+- 10/22/2018 - Community Day EclipseCon Europe
+ 2018 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2018.html)
+- 10/21/2019 - Community Day EclipseCon Europe
+ 2019 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2019.html)
+- 10/19/2020 - Community Day EclipseCon Europe
+ 2020 - [slides](https://www.eclipse.org/hawkbit/slides/community-day-2020.html)
## Articles
-- 10/27/2015 - Why software provisioning goes open source - [article](http://blog.bosch-si.com/categories/technology/2015/10/software-provisioning-goes-open-source-find/)
-- 05/25/2016 - jaxenter: Eclipse hawkBit - [english](https://jaxenter.com/eclipse-hawkbit-126445.html) - [german](https://jaxenter.de/eclipse-hawkbit-46372)
-- 09/27/2016 - Eclipse Newsletter - 'IoT is the new black' - [article](http://www.eclipse.org/community/eclipse_newsletter/2016/september/article2.php)
+- 10/27/2015 - Why software provisioning goes open
+ source - [article](http://blog.bosch-si.com/categories/technology/2015/10/software-provisioning-goes-open-source-find/)
+- 05/25/2016 - jaxenter: Eclipse
+ hawkBit - [english](https://jaxenter.com/eclipse-hawkbit-126445.html) - [german](https://jaxenter.de/eclipse-hawkbit-46372)
+- 09/27/2016 - Eclipse Newsletter - 'IoT is the new
+ black' - [article](http://www.eclipse.org/community/eclipse_newsletter/2016/september/article2.php)
## Ask a question
-Visit [stackoverflow.com](https://stackoverflow.com/questions/tagged/eclipse-hawkbit) to find questions or raise your own tagged with `eclipse-hawkbit`.
+Visit [stackoverflow.com](https://stackoverflow.com/questions/tagged/eclipse-hawkbit) to find questions or raise your
+own tagged with `eclipse-hawkbit`.
## Chat
-Searching for a quick response from the team behind hawkBit and the hawkBit community, join the [Gitter Chat](https://gitter.im/eclipse/hawkbit).
+Searching for a quick response from the team behind hawkBit and the hawkBit community, join
+the [Gitter Chat](https://gitter.im/eclipse/hawkbit).
## Mailing List
-A great way to stay up to date with hawkBit activity is to subscribe to the Mailing list provided by Eclipse. Sign up for the mailing list [here](https://dev.eclipse.org/mailman/listinfo/hawkbit-dev).
+A great way to stay up to date with hawkBit activity is to subscribe to the Mailing list provided by Eclipse. Sign up
+for the mailing list [here](https://dev.eclipse.org/mailman/listinfo/hawkbit-dev).
## Issue Tracker
-Issues and bugs related to hawkBit are tracked with the Github Issue tracking system. If you find any issues, please report them [here](https://github.com/eclipse-hawkbit/hawkbit/issues).
+Issues and bugs related to hawkBit are tracked with the Github Issue tracking system. If you find any issues, please
+report them [here](https://github.com/eclipse-hawkbit/hawkbit/issues).
## Contributing
-An overview of the contribution process is [here](https://wiki.eclipse.org/Development_Resources/Contributing_via_Git). Checkout the [Contribution Guidelines](https://github.com/eclipse-hawkbit/hawkbit/blob/master/CONTRIBUTING.md) on the Eclipse hawkBit GitHub Repository.
+An overview of the contribution process is [here](https://wiki.eclipse.org/Development_Resources/Contributing_via_Git).
+Checkout the [Contribution Guidelines](https://github.com/eclipse-hawkbit/hawkbit/blob/master/CONTRIBUTING.md) on the
+Eclipse hawkBit GitHub Repository.
diff --git a/site/content/concepts/authentication.md b/site/content/concepts/authentication.md
index 5ca952b72..d6b22f1da 100644
--- a/site/content/concepts/authentication.md
+++ b/site/content/concepts/authentication.md
@@ -9,17 +9,21 @@ A hawkBit update server can be accessed in four different ways:
- _Direct Device Integration (DDI) API_ by **targets**.
- _Management API_ by 3rd party **applications**.
- _Device Management Federation (DMF) API_ by 3rd party **applications** through AMQP.
-
+
## DDI API Authentication Modes
### Security Token
-hawkBit supports multiple ways to authenticate a target against the server. The different authentication modes can be individual enabled and disabled within hawkBit. Both on system level (with Spring Boot properties) as per individual tenant.
+hawkBit supports multiple ways to authenticate a target against the server. The different authentication modes can be
+individual enabled and disabled within hawkBit. Both on system level (with Spring Boot properties) as per individual
+tenant.
#### Target Security Token Authentication
-There is a 32 alphanumeric character security-token for each created target within IoT hawkBit. This token can be used to authenticate the target at hawkBit through the HTTP-Authorization header with the custom scheme _TargetToken_.
+
+There is a 32 alphanumeric character security-token for each created target within IoT hawkBit. This token can be used
+to authenticate the target at hawkBit through the HTTP-Authorization header with the custom scheme _TargetToken_.
```
GET /SPDEMO/controller/v1/0e945f95-9117-4500-9b0a-9c6d72fa6c07 HTTP/1.1
@@ -27,18 +31,28 @@ Host: your.hawkBit.server
Authorization: TargetToken bH7XXAprK1ChnLfKSdtlsp7NOlPnZAYY
```
-The target security token is provided in [DMF API](../../apis/dmf_api/) as part of the update message in order to allow DMF clients to leverage the feature or can it be manually retrieved per target by [Management API](../../apis/management_api/) or in the [Management UI](../../ui) in the target details.
+The target security token is provided in [DMF API](../../apis/dmf_api/) as part of the update message in order to allow
+DMF clients to leverage the feature or can it be manually retrieved per target
+by [Management API](../../apis/management_api/) or in the [Management UI](../../ui) in the target details.
-Note: needs to be enabled in your hawkBit installation **and** in the tenant configuration. That allows both the operator as well as the individual customer (if run in a multi-tenant setup) to enable this access method. See [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java) for system wide enablement.
+Note: needs to be enabled in your hawkBit installation **and** in the tenant configuration. That allows both the
+operator as well as the individual customer (if run in a multi-tenant setup) to enable this access method.
+See [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java)
+for system wide enablement.
The additional activation for the individual tenant:

#### Gateway Security Token Authentication
-Often the targets are connected through a gateway which manages the targets directly and as a result are indirectly connected to the hawkBit update server.
-To authenticate this gateway and allow it to manage all target instances under its tenant there is a _GatewayToken_ to authenticate this gateway through the HTTP-Authorization header with a custom scheme _GatewayToken_. This is of course also handy during development or for testing purposes. However, we generally recommend to use this token with care as it allows to act _in the name of_ any device.
+Often the targets are connected through a gateway which manages the targets directly and as a result are indirectly
+connected to the hawkBit update server.
+
+To authenticate this gateway and allow it to manage all target instances under its tenant there is a _GatewayToken_ to
+authenticate this gateway through the HTTP-Authorization header with a custom scheme _GatewayToken_. This is of course
+also handy during development or for testing purposes. However, we generally recommend to use this token with care as it
+allows to act _in the name of_ any device.
```
GET /SPDEMO/controller/v1/0e945f95-9117-4500-9b0a-9c6d72fa6c07 HTTP/1.1
@@ -46,16 +60,24 @@ Host: your.hawkBit.server
Authorization: GatewayToken 3nkswAZhX81oDtktq0FF9Pn0Tc0UGXPW
```
-Note: needs to be enabled in your hawkBit installation **and** in the tenant configuration. That allows both the operator as well as the individual customer (if run in a multi-tenant setup) to enable this access method. See [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java) for system wide enablement.
+Note: needs to be enabled in your hawkBit installation **and** in the tenant configuration. That allows both the
+operator as well as the individual customer (if run in a multi-tenant setup) to enable this access method.
+See [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java)
+for system wide enablement.
The additional activation for the individual tenant:

#### Anonymous access
-Here we offer general anonymous access for all targets (see [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java)) which we consider not really sufficient for a production system but it might come in handy to get a project started in the beginning.
-However, anonymous download on the other side might be interesting even in production for scenarios where the artifact itself is already encrypted.
+Here we offer general anonymous access for all targets (
+see [DdiSecurityProperties](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DdiSecurityProperties.java))
+which we consider not really sufficient for a production system but it might come in handy to get a project started in
+the beginning.
+
+However, anonymous download on the other side might be interesting even in production for scenarios where the artifact
+itself is already encrypted.
The activation for the individual tenant:
@@ -63,15 +85,24 @@ The activation for the individual tenant:
### Certificate Authentication by Reverse Proxy
-hawkBit offers a certificate-based authentication mechanism, also known as mutual TLS (mTLS), which eliminates the need to share a security token with the server. To implement this, you'll require a reverse proxy deployed in front of the hawkBit server to handle authentication. This process involves obtaining certificates (and keys) for both the client and the reverse proxy and configuring hawkBit accordingly.
+hawkBit offers a certificate-based authentication mechanism, also known as mutual TLS (mTLS), which eliminates the need
+to share a security token with the server. To implement this, you'll require a reverse proxy deployed in front of the
+hawkBit server to handle authentication. This process involves obtaining certificates (and keys) for both the client and
+the reverse proxy and configuring hawkBit accordingly.
-Initially, you'll need to obtain certificates (and keys) for these components from the same or different Certificate Authorities (CAs). Once you have acquired certificates you have to set them up to both the client and the hawkBit server.
+Initially, you'll need to obtain certificates (and keys) for these components from the same or different Certificate
+Authorities (CAs). Once you have acquired certificates you have to set them up to both the client and the hawkBit
+server.
-Then you shall enable *Allow targets to authenticate via a certificate authenticated by a reverse proxy* and set the fingerprint of the client certificate issuer(s) (as a comma separated list).
+Then you shall enable *Allow targets to authenticate via a certificate authenticated by a reverse proxy* and set the
+fingerprint of the client certificate issuer(s) (as a comma separated list).
To authenticate the request to hawBit the following condition shall be met:
+
- the common name of the client certificate shall match the controller/client id
-- the SSL Issuer(s) hash of the presented client certificate shall be set for the tenant. For that, in Hawkbit's UI section, under system configuration, you shall enable 'Allow targets to authenticate via a certificate by an reverse proxy' and set the hash of the client certificate issuer(s) (as a comma separated list).
+- the SSL Issuer(s) hash of the presented client certificate shall be set for the tenant. For that, in Hawkbit's UI
+ section, under system configuration, you shall enable 'Allow targets to authenticate via a certificate by an reverse
+ proxy' and set the hash of the client certificate issuer(s) (as a comma separated list).

@@ -81,7 +112,8 @@ You can use the following command to get the issuer hash:
openssl x509 -in client_certificate.crt -issuer_hash -noout`
```
-Here is an example diagram that shows all the communication between the hawkBit, reverse proxy and client. For the sake of simplification we assume that there are not intermediate certificates and the certificate and key are as follows:
+Here is an example diagram that shows all the communication between the hawkBit, reverse proxy and client. For the sake
+of simplification we assume that there are not intermediate certificates and the certificate and key are as follows:
- client_ca.crt signs client.crt
- server_ca.crt signs server.crt
@@ -93,25 +125,37 @@ Here is an example diagram that shows all the communication between the hawkBit,
#### Example - Nginx Reverse Proxy Configurations
-Nginx doesn't support obtaining the issuer hash without addons. Therefore, in this example we bypass sending real SSL Issuer hash to hawhBit but do certificate issuer validation at Nginx and then supply shared (between Nginx and hawkBit) fixed hash "Hawkbit". You could use any value here as long as it is matched with the *Allow targets to authenticate via a certificate authenticated by a reverse proxy* setting in the hawkBit UI. Note that for multi-tenant scenarios with different trusted CAs this example won't work.
+Nginx doesn't support obtaining the issuer hash without addons. Therefore, in this example we bypass sending real SSL
+Issuer hash to hawhBit but do certificate issuer validation at Nginx and then supply shared (between Nginx and hawkBit)
+fixed hash "Hawkbit". You could use any value here as long as it is matched with the *Allow targets to authenticate via
+a certificate authenticated by a reverse proxy* setting in the hawkBit UI. Note that for multi-tenant scenarios with
+different trusted CAs this example won't work.
1. Hawkbit Configurations
There are also some configurations that you need update when you deployed your hawkbit service.
- You need to add the given setting to your hawkBit configurations so that hawkBit can generate the URLs according to the https that the client will use to download. If you're deploying hawkBit as a Docker container, add these configurations as environmental values in the docker-compose.yml file.
+ You need to add the given setting to your hawkBit configurations so that hawkBit can generate the URLs according to
+ the https that the client will use to download. If you're deploying hawkBit as a Docker container, add these
+ configurations as environmental values in the docker-compose.yml file.
```
server.forward-headers-strategy=NATIVE
```
-2. In Hawkbit's UI section, under system configuration, make sure to select *Allow targets to authenticate via a certificate authenticated by a reverse proxy* and input the fixed issuer hash as "Hawkbit". This can be whetever you have configured in the nginx configuration in `proxy_set_header X-Ssl-Issuer-Hash-1` below.
+2. In Hawkbit's UI section, under system configuration, make sure to select *Allow targets to authenticate via a
+ certificate authenticated by a reverse proxy* and input the fixed issuer hash as "Hawkbit". This can be whetever you
+ have configured in the nginx configuration in `proxy_set_header X-Ssl-Issuer-Hash-1` below.
-3. After placing your certificates and keys, you need to deploy your proxy server and apply the provided configurations. You can apply mutual TLS specifically to the URL given below to implement the process only for devices using the Device Integration API:
+3. After placing your certificates and keys, you need to deploy your proxy server and apply the provided configurations.
+ You can apply mutual TLS specifically to the URL given below to implement the process only for devices using the
+ Device Integration API:
- `hawkbit.dev.example.com/default/controller/`
+ `hawkbit.dev.example.com/default/controller/`
- This ensures that other clients, like UI users, can connect to hawkBit without requiring client certificates. They can use Username and Password in the Management API, eliminating the need for authentication and making it more user-friendly.
+ This ensures that other clients, like UI users, can connect to hawkBit without requiring client certificates. They
+ can use Username and Password in the Management API, eliminating the need for authentication and making it more
+ user-friendly.
```nginx
# Nginx Hawkbit Configurations
@@ -185,7 +229,7 @@ server {
}
}
```
-
+
4. To deploy Nginx, you could use a `.yml` file. Here's an example `docker-compose.yml` file for Nginx Docker.
```yml
@@ -210,14 +254,21 @@ services:
- ./certbot/www/:/var/www/certbot/:rw
- ./certbot/conf/:/etc/letsencrypt/:rw
```
-`/client-cer/:/etc/nginx/client-cer/` is the designated location for the certificate authority that has signed the client certificate. The presented client certificate will be verified against this CA.
-5. After successfully generating your certificates with the correct chain, deploying your Nginx and Hawkbit services with appropriate configurations, and updating the settings on the device side, you will be able to establish a certificate-based authentication mechanism. This will eliminate the necessity of sharing a security token with the server.
-
+`/client-cer/:/etc/nginx/client-cer/` is the designated location for the certificate authority that has signed the
+client certificate. The presented client certificate will be verified against this CA.
+
+5. After successfully generating your certificates with the correct chain, deploying your Nginx and Hawkbit services
+ with appropriate configurations, and updating the settings on the device side, you will be able to establish a
+ certificate-based authentication mechanism. This will eliminate the necessity of sharing a security token with the
+ server.
+
+
##### Swupdate Suricatta Configurations
-If the client is utilizing the SWUpdate Suricatta service, the configurations on the device or client side should also be adjusted as follows. Remember to change id, url and certificate names to your needs.
+If the client is utilizing the SWUpdate Suricatta service, the configurations on the device or client side should also
+be adjusted as follows. Remember to change id, url and certificate names to your needs.
The location of the config file is `/etc/swupdate/swupdate.conf`
@@ -241,6 +292,7 @@ journalctl --follow -u swupdate
```
+
##### Testing
You can test the communication by using the Curl command below to see if you successfully implemented mutual TLS:
@@ -249,14 +301,18 @@ You can test the communication by using the Curl command below to see if you suc
curl -L -v --cert client.crt --key client.key --cacert server_ca.crt https://hawkbit.dev.example.com/default/controller/v1/{device-id}
```
-In the UI, after uploading an SWU package and requesting a firmware update, you can use the link below to attempt to install the software package.
+In the UI, after uploading an SWU package and requesting a firmware update, you can use the link below to attempt to
+install the software package.
```
curl -L -v --cert client.crt --key client.key --cacert server_ca.crt https://hawkbit.dev.example.com/default/controller/v1/{device-id}/softwaremodules/{artifact-id}/artifacts/hawkbit_updated_5.swu --output outputfile
```
## DMF API
-Authentication is provided by _RabbitMQ_ [vhost and user credentials](https://www.rabbitmq.com/access-control.html) that is used for the integration.
+
+Authentication is provided by _RabbitMQ_ [vhost and user credentials](https://www.rabbitmq.com/access-control.html) that
+is used for the integration.
## Management API
+
- Basic Auth
diff --git a/site/content/concepts/authorization.md b/site/content/concepts/authorization.md
index 5688930b1..f90f9c546 100644
--- a/site/content/concepts/authorization.md
+++ b/site/content/concepts/authorization.md
@@ -4,12 +4,22 @@ parent: Concepts
weight: 52
---
-Authorization is handled separately for _Direct Device Integration (DDI) API_ and _Device Management Federation (DMF) API_ (where successful authentication includes full authorization) and _Management API_ and _UI_ which is based on Spring security [authorities](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java).
+Authorization is handled separately for _Direct Device Integration (DDI) API_ and _Device Management Federation (DMF)
+API_ (where successful authentication includes full authorization) and _Management API_ and _UI_ which is based on
+Spring
+security [authorities](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/im/authentication/SpPermission.java).
-However, keep in mind that hawkBit does not offer an off the shelf authentication provider to leverage these permissions and the underlying multi user/tenant capabilities of hawkBit but it supports authentication providers offering an OpenID Connect interface. Check out [Spring security documentation](http://projects.spring.io/spring-security/) for further information. In hawkBit [SecurityAutoConfiguration](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-autoconfigure/src/main/java/org/eclipse/hawkbit/autoconfigure/security/SecurityAutoConfiguration.java) is a good starting point for integration.
+However, keep in mind that hawkBit does not offer an off the shelf authentication provider to leverage these permissions
+and the underlying multi user/tenant capabilities of hawkBit but it supports authentication providers offering an OpenID
+Connect interface. Check out [Spring security documentation](http://projects.spring.io/spring-security/) for further
+information. In
+hawkBit [SecurityAutoConfiguration](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-autoconfigure/src/main/java/org/eclipse/hawkbit/autoconfigure/security/SecurityAutoConfiguration.java)
+is a good starting point for integration.
-The default implementation is single user/tenant with basic auth and the logged in user is provided with all permissions. Additionally, the application properties may be configured for multiple static users; see [Multiple Users](#multiple-users) for details.
+The default implementation is single user/tenant with basic auth and the logged in user is provided with all
+permissions. Additionally, the application properties may be configured for multiple static users;
+see [Multiple Users](#multiple-users) for details.
## DDI API
@@ -19,13 +29,16 @@ An authenticated target is permitted to:
- provide feedback to the the server
- download artifacts that are assigned to it
-A target might be permitted to download artifacts without authentication (if enabled, see above). Only the download can be permitted to disable the authentication. This can be used in scenarios where the artifacts itself are e.g. signed and secured.
+A target might be permitted to download artifacts without authentication (if enabled, see above). Only the download can
+be permitted to disable the authentication. This can be used in scenarios where the artifacts itself are e.g. signed and
+secured.
## Management API and UI
### Multiple Users
-hawkBit optionally supports configuring multiple static users through the application properties. In this case, the user and password Spring security properties are ignored.
+hawkBit optionally supports configuring multiple static users through the application properties. In this case, the user
+and password Spring security properties are ignored.
An example configuration is given below.
hawkbit.server.im.users[0].username=admin
@@ -42,46 +55,54 @@ An example configuration is given below.
hawkbit.server.im.users[1].email=test@tester.com
hawkbit.server.im.users[1].permissions=READ_TARGET,UPDATE_TARGET,CREATE_TARGET,DELETE_TARGET
-A permissions value of `ALL` will provide that user with all possible permissions. Passwords need to be specified with the used password encoder in brackets. In this example, `noop` is used as the plaintext encoder. For production use, it is recommended to use a hash function designed for passwords such as *bcrypt*. See this [blog post](https://spring.io/blog/2017/11/01/spring-security-5-0-0-rc1-released#password-storage-format) for more information on password encoders in Spring Security.
+A permissions value of `ALL` will provide that user with all possible permissions. Passwords need to be specified with
+the used password encoder in brackets. In this example, `noop` is used as the plaintext encoder. For production use, it
+is recommended to use a hash function designed for passwords such as *bcrypt*. See
+this [blog post](https://spring.io/blog/2017/11/01/spring-security-5-0-0-rc1-released#password-storage-format) for more
+information on password encoders in Spring Security.
### OpenID Connect
-hawkbit supports authentication providers which use the OpenID Connect standard, an authentication layer built on top of the OAuth 2.0 protocol.
+hawkbit supports authentication providers which use the OpenID Connect standard, an authentication layer built on top of
+the OAuth 2.0 protocol.
An example configuration is given below.
spring.security.oauth2.client.registration.oidc.client-id=clientID
spring.security.oauth2.client.provider.oidc.issuer-uri=https://oidc-provider/issuer-uri
spring.security.oauth2.client.provider.oidc.jwk-set-uri=https://oidc-provider/jwk-set-uri
-Note: at the moment only DEFAULT tenant is supported. By default the resource_access//roles claim is mapped to hawkBit permissions. However, by registering a Spring bean _org.eclipse.hawkbit.autoconfigure.security.OidcUserManagementAutoConfiguration.JwtAuthoritiesExtractor_ a custom extractor permission mapper could be registered.
+Note: at the moment only DEFAULT tenant is supported. By default the resource_access//roles claim is mapped
+to hawkBit permissions. However, by registering a Spring bean
+_org.eclipse.hawkbit.autoconfigure.security.OidcUserManagementAutoConfiguration.JwtAuthoritiesExtractor_ a custom
+extractor permission mapper could be registered.
### Delivered Permissions
- READ_/UPDATE_/CREATE_/DELETE_TARGET for:
- - Target entities including metadata (that includes also the installed and assigned distribution sets)
- - Target tags
- - Target actions
- - Target registration rules
- - Bulk operations
- - Target filters
+ - Target entities including metadata (that includes also the installed and assigned distribution sets)
+ - Target tags
+ - Target actions
+ - Target registration rules
+ - Bulk operations
+ - Target filters
- READ_/UPDATE_/CREATE_/DELETE_REPOSITORY for:
- - Distribution sets
- - Software Modules
- - Artifacts
- - DS tags
+ - Distribution sets
+ - Software Modules
+ - Artifacts
+ - DS tags
- READ_TARGET_SECURITY_TOKEN
- - Permission to read the target security token. The security token is security concerned and should be protected.
+ - Permission to read the target security token. The security token is security concerned and should be protected.
- DOWNLOAD_REPOSITORY_ARTIFACT
- - Permission to download artifacts of a software module (Note: READ_REPOSITORY allows only to read the metadata).
+ - Permission to download artifacts of a software module (Note: READ_REPOSITORY allows only to read the metadata).
- TENANT_CONFIGURATION
- - Permission to administrate the tenant settings.
+ - Permission to administrate the tenant settings.
- READ_/UPDATE_/CREATE_/DELETE_/HANDLE_/APPROVE_ROLLOUT for:
- - Managing rollouts and provision targets through a rollout.
+ - Managing rollouts and provision targets through a rollout.
### Permission Matrix for example uses cases that need more than one permission
@@ -95,4 +116,6 @@ Note: at the moment only DEFAULT tenant is supported. By default the resource_ac
## Device Management Federation API
-The provided _RabbitMQ_ [vhost and user](https://www.rabbitmq.com/access-control.html) should be provided with the necessary permissions to send messages to hawkBit through the exchange and receive messages from it through the specified queue.
+The provided _RabbitMQ_ [vhost and user](https://www.rabbitmq.com/access-control.html) should be provided with the
+necessary permissions to send messages to hawkBit through the exchange and receive messages from it through the
+specified queue.
diff --git a/site/content/concepts/datamodel.md b/site/content/concepts/datamodel.md
index 8aed1525d..9a226e93b 100644
--- a/site/content/concepts/datamodel.md
+++ b/site/content/concepts/datamodel.md
@@ -4,18 +4,30 @@ parent: Concepts
weight: 53
---
-The hawkBit data model was designed to have enough flexibility to define complex software structures (e.g. operating system, runtimes, apps, different kind of artifacts) on one side and simplicity compared to the capabilities of a full blown configuration management on the other.
+The hawkBit data model was designed to have enough flexibility to define complex software structures (e.g. operating
+system, runtimes, apps, different kind of artifacts) on one side and simplicity compared to the capabilities of a full
+blown configuration management on the other.
-It does define a hierarchy of software that starts with a distribution, which can have (sub-)modules and these may have multiple artifacts. However, it does not consider any kind of dependency definitions between modules or artifacts. As a result, dependency checks - if necessary - have to be done outside hawkBit, i.e. on the device itself or before the entity creation in hawkBit by the origin.
+It does define a hierarchy of software that starts with a distribution, which can have (sub-)modules and these may have
+multiple artifacts. However, it does not consider any kind of dependency definitions between modules or artifacts. As a
+result, dependency checks - if necessary - have to be done outside hawkBit, i.e. on the device itself or before the
+entity creation in hawkBit by the origin.
## Provisioning Target Definition
-A Provisioning Target is a neutral definition that may be an actual real device (e.g. gateway, embedded sensor) or a virtual device (e.g. vehicle, smart home).
+A Provisioning Target is a neutral definition that may be an actual real device (e.g. gateway, embedded sensor) or a
+virtual device (e.g. vehicle, smart home).
-The definition in hawkBit might reflect the transactional behavior if necessary on the device side. A vehicle might be updated device by device or as a whole. As a result one way of defining a vehicle in hawkBit could be to have one all inclusive Software Module or one module per (sub-) device.
+The definition in hawkBit might reflect the transactional behavior if necessary on the device side. A vehicle might be
+updated device by device or as a whole. As a result one way of defining a vehicle in hawkBit could be to have one all
+inclusive Software Module or one module per (sub-) device.
-A Target can have, next to its defined properties (e.g. controller ID, target type, name, description, security token), a generic set of attributes and meta data, both in key:value format. Target attributes are owned and managed by the device whereas target meta data are managed by the operator. If a target is defined to be of a certain target type, then during the assignment of a distribution set, a compatibility check will be performed between the target type and distribution set type.
+A Target can have, next to its defined properties (e.g. controller ID, target type, name, description, security token),
+a generic set of attributes and meta data, both in key:value format. Target attributes are owned and managed by the
+device whereas target meta data are managed by the operator. If a target is defined to be of a certain target type, then
+during the assignment of a distribution set, a compatibility check will be performed between the target type and
+distribution set type.
## Software Structure Definition
@@ -23,28 +35,38 @@ The structure defines the model of the supported software by the provisioning ta
- Distribution Set Type:defines a package structure that is supported by certain devices
- Consists of Software Module Types both for
- - Firmware - device can have only one module of that type (e.g. the operating system)
- - Software - device can have multiple modules of that type (e.g. "Apps")
+ - Firmware - device can have only one module of that type (e.g. the operating system)
+ - Software - device can have multiple modules of that type (e.g. "Apps")
Software Content Definition:
- Distribution Set: can be deployed to a provisioning target
- Software Module: is a sub element of the distribution, e.g. OS, application, firmware X, firmware Y
-- Artifact: binaries for a software module. Note: the decision which artifacts have to be downloaded are done on the device side, e.g. Full package, signatures, binary deltas
-
+- Artifact: binaries for a software module. Note: the decision which artifacts have to be downloaded are done on the
+ device side, e.g. Full package, signatures, binary deltas
## Entity Relationships
+
The public defined entities and their relation which are reflected by the Management API.
-
-
## Deleting and Archiving Software Modules
-When a user deletes a Software Module, the update server cannot simply remove all the corresponding data. Because when the Software Module is already assigned to a Distribution Set or was assigned to a Target in the past, the hawkBit server has to make sure that remains a clean and full update history for every target. The history contains all information (e.g. name, version) of the software, which was assigned to a specific Target. Obviously storing the binary data of the artifacts is not necessary for the history purpose.
-The delete process which is performed, when there are historical connections to targets is called SoftDelete. This process marks the Software Module as deleted and removes the artifact, but it won't delete the meta data, which describes the SoftwareModule and the associated Artifacts. SoftwareModules, which are marked as delete won't be visible for the user, when he is requesting all SoftwareModules.
+When a user deletes a Software Module, the update server cannot simply remove all the corresponding data. Because when
+the Software Module is already assigned to a Distribution Set or was assigned to a Target in the past, the hawkBit
+server has to make sure that remains a clean and full update history for every target. The history contains all
+information (e.g. name, version) of the software, which was assigned to a specific Target. Obviously storing the binary
+data of the artifacts is not necessary for the history purpose.
-Just in case there are no connections to Distribution Sets and targets the server will perform a HardDelete. This process deletes all stored data, including all meta information.
+The delete process which is performed, when there are historical connections to targets is called SoftDelete. This
+process marks the Software Module as deleted and removes the artifact, but it won't delete the meta data, which
+describes the SoftwareModule and the associated Artifacts. SoftwareModules, which are marked as delete won't be visible
+for the user, when he is requesting all SoftwareModules.
+
+Just in case there are no connections to Distribution Sets and targets the server will perform a HardDelete. This
+process deletes all stored data, including all meta information.
{{% note %}}
-In case of a SoftDelete the unique constraints are still in place, i.e. you cannot create an entity with the same name/key. This constraint might be removed in future versions because of the impact on the user experience (i.e. he does not see the soft deleted module but cannot create a new one).
+In case of a SoftDelete the unique constraints are still in place, i.e. you cannot create an entity with the same
+name/key. This constraint might be removed in future versions because of the impact on the user experience (i.e. he does
+not see the soft deleted module but cannot create a new one).
{{% /note %}}
\ No newline at end of file
diff --git a/site/content/concepts/rollout-management.md b/site/content/concepts/rollout-management.md
index a809aeaac..936d48779 100644
--- a/site/content/concepts/rollout-management.md
+++ b/site/content/concepts/rollout-management.md
@@ -12,9 +12,9 @@ That includes:
- _Technical Scalability_ by means of horizontal scale of the hawkBit server cluster in the cloud.
- _Global_ artifact _content delivery_ capacities.
- _Functional Scalability_ by means of:
- - Secure handling of large volumes of devices at rollout creation time.
- - Monitoring of the rollout progress.
- - Emergency rollout shutdown in case of problems on to many devices.
+ - Secure handling of large volumes of devices at rollout creation time.
+ - Monitoring of the rollout progress.
+ - Emergency rollout shutdown in case of problems on to many devices.
- Reporting capabilities for a complete understanding of the rollout progress at each point in time.
@@ -23,44 +23,58 @@ Eclipse hawkBit sees these capabilities under the term Rollout Management.
The following capabilities are currently supported by the _Rollout Management_:
- Create, update and start of rollouts.
- - Selection of targets as input for the rollout based on _target filter_ functionality.
- - Selection of a _DistributionSet_.
- - Auto-splitting of the input target list into a defined number deployment groups.
+ - Selection of targets as input for the rollout based on _target filter_ functionality.
+ - Selection of a _DistributionSet_.
+ - Auto-splitting of the input target list into a defined number deployment groups.
- Approval workflow
- - Has to be enabled explicitly in configuration.
- - Enables a workflow that requires a user with adequate permissions to review any new or updated rollout before it
- can be started.
- - Allows integration with 3rd party workflow engines.
-
+ - Has to be enabled explicitly in configuration.
+ - Enables a workflow that requires a user with adequate permissions to review any new or updated rollout before it
+ can be started.
+ - Allows integration with 3rd party workflow engines.
+
- Cascading start of the deployment groups based on installation status of the previous group.
- Emergency shutdown of the rollout in case a group exceeds the defined error threshold.
- Rollout progress monitoring for the entire rollout and the individual groups.
-
## Cascading Deployment Group Execution
+
The cascading execution of the deployment groups is based on two thresholds that can be defined by the rollout creator.
+
- success condition by means of percentage of successfully installed targets in the current groups triggers.
-- error condition by means of absolute or percentage of failed installations which triggers an emergency shutdown of the entire rollout.
+- error condition by means of absolute or percentage of failed installations which triggers an emergency shutdown of the
+ entire rollout.
## Rollout state machine
### State Machine on Rollout
+

### State Machine on Rollout Deployment Group
+

## Multi-Assignments (beta)
-One of the main paradigms of Eclipse hawkBit is, that a Distribution Set represents the currently installed software of a device. Hence, a device can have only one Distribution Set assigned/installed at a time. With _Multi-Assignments_ enabled, this paradigm shifts. Multi-Assignments allows to assign multiple Distribution Sets to a device simultaneously, without cancelling each other. As a consequence, an operator can trigger multiple campaigns addressing the same devices in parallel.
+One of the main paradigms of Eclipse hawkBit is, that a Distribution Set represents the currently installed software of
+a device. Hence, a device can have only one Distribution Set assigned/installed at a time. With _Multi-Assignments_
+enabled, this paradigm shifts. Multi-Assignments allows to assign multiple Distribution Sets to a device simultaneously,
+without cancelling each other. As a consequence, an operator can trigger multiple campaigns addressing the same devices
+in parallel.
### Action weight
-To differentiate between important and less important updates a property called _weight_ is used. When multi-assignments is enabled every action has a weight value between (and including) 0 and 1000. The higher the weight the more important is the assignment represented by the action. Also when defining a _rollout_ or an _auto-assignment_ and multi-assignments is enabled a weight value has to be provided. This value is passed to the actions created during the execution of these _rollouts_ and _auto-assignments_. If no weight was provided the highest value of 1000 is used instead.
+To differentiate between important and less important updates a property called _weight_ is used. When multi-assignments
+is enabled every action has a weight value between (and including) 0 and 1000. The higher the weight the more important
+is the assignment represented by the action. Also when defining a _rollout_ or an _auto-assignment_ and
+multi-assignments is enabled a weight value has to be provided. This value is passed to the actions created during the
+execution of these _rollouts_ and _auto-assignments_. If no weight was provided the highest value of 1000 is used
+instead.
### Consequences
-While this feature provides more flexibility to the user and enables new use-cases, there are also some consequences one should be aware of:
+While this feature provides more flexibility to the user and enables new use-cases, there are also some consequences one
+should be aware of:
**Critical**
@@ -69,9 +83,12 @@ While this feature provides more flexibility to the user and enables new use-cas
**Minor**
-* While on DMF-API a MULTI_ACTION request is sent, DDI-API only exposes the next action which has the highest priority in the list of open actions(according to their weight property).
-* All information regarding the currently assigned or installed Distribution Set does only respect the last assignment, as well as the last successfully installed Distribution set. This also affects:
+* While on DMF-API a MULTI_ACTION request is sent, DDI-API only exposes the next action which has the highest priority
+ in the list of open actions(according to their weight property).
+* All information regarding the currently assigned or installed Distribution Set does only respect the last assignment,
+ as well as the last successfully installed Distribution set. This also affects:
* Pinning a target or Distribution Set in Deployment View.
* Statistics about installed or assigned Distribution Sets.
-* Auto close running actions, when a new Distribution Set is assigned (`repository.actions.autoclose.enabled`) is deactivated.
+* Auto close running actions, when a new Distribution Set is assigned (`repository.actions.autoclose.enabled`) is
+ deactivated.
* Marking a Distribution Set to be a *Required Migration Step* is deactivated.
\ No newline at end of file
diff --git a/site/content/concepts/targetstate.md b/site/content/concepts/targetstate.md
index fab899a87..2544f2c4d 100644
--- a/site/content/concepts/targetstate.md
+++ b/site/content/concepts/targetstate.md
@@ -4,7 +4,10 @@ parent: Concepts
weight: 55
---
-A target has a current state which reflects the provisioning status of the device at this point in time. State changes are driven either by the update server by means of starting an update or by the controller on the provisioning target that gives feedback to the update server, e.g. "I am here", "I am working on a provisioning", "I have finished a provisioning".
+A target has a current state which reflects the provisioning status of the device at this point in time. State changes
+are driven either by the update server by means of starting an update or by the controller on the provisioning target
+that gives feedback to the update server, e.g. "I am here", "I am working on a provisioning", "I have finished a
+provisioning".
## Defined states
@@ -18,4 +21,5 @@ A target has a current state which reflects the provisioning status of the devic
| REGISTERED | Target registered at the update server but no _Distribution Set_ assigned. Is the initial starting point for plug-and-play devices. |
## Transitions
+

diff --git a/site/content/features.md b/site/content/features.md
index 94c75bcce..ec77de0d8 100644
--- a/site/content/features.md
+++ b/site/content/features.md
@@ -3,30 +3,35 @@ title: Features
weight: 40
---
-
## Device and Software Repository
+
- Repository that holds the provisioning targets and assignable software distributions.
- Targets to be logically grouped by Target Types.
- That includes a full software update history for every device.
-- Support for pre-commission devices in the repository and plug and play, i.e. device is created if it is authenticated for the first time.
+- Support for pre-commission devices in the repository and plug and play, i.e. device is created if it is authenticated
+ for the first time.
## Update Management
+
- Directly deploy a defined software distribution to a device (by Management API).
- Update handling is independent of the device type, integration approach or connectivity.
-- Optional user consent flow, download and install updates only after respective end user has confirmed it.
+- Optional user consent flow, download and install updates only after respective end user has confirmed it.
- Mass cancel the distribution of an update by invalidating the distribution set.
- Use action status codes for easier analysis.
## Artifact Content Delivery
+
- Partial downloads supported.
- Download resume supported (RFC7233).
- Content management by RESTful API and UI (see above).
-- Authorization based on software assignment, i.e. a device can only download what has been assigned to it in the first place.
+- Authorization based on software assignment, i.e. a device can only download what has been assigned to it in the first
+ place.
- Delta artifact hosting supported.
- Artifact signature hosting supported.
- Plug-point for artifact encryption allowing to encrypt artifacts on upload.
## Rollout/Campaign Management
+
- Secure handling of large volumes of devices at rollout creation time.
- Flexible deployment group definition as part of a rollout.
- Monitoring of the rollout progress.
@@ -36,6 +41,7 @@ weight: 40
## Interfaces
### Management API
+
- RESTful API
- Create/Read/Update/Delete operations for provisioning targets (i.e. devices) and repository content (i.e. software).
- Manage and monitor software update operations.
@@ -44,6 +50,7 @@ weight: 40
- Supports filtering, sorting and paging.
### Direct Device Integration API
+
- RESTful HTTP based API for direct device integration
- JSON payload.
- Traffic optimized (content based Etag generation, not modified).
@@ -51,7 +58,9 @@ weight: 40
- TLS encryption.
### Device Management Federation API
+
- Indirect device integration through a device management service or application into hawkBit.
-- Optimized for high service to service throughput with [AMQP](https://www.rabbitmq.com/amqp-0-9-1-reference.html) messaging interface.
+- Optimized for high service to service throughput with [AMQP](https://www.rabbitmq.com/amqp-0-9-1-reference.html)
+ messaging interface.
- Separate AMQP vHost per tenant for maximum security.
diff --git a/site/content/gettingstarted.md b/site/content/gettingstarted.md
index 3b874b034..640c2e0d6 100755
--- a/site/content/gettingstarted.md
+++ b/site/content/gettingstarted.md
@@ -16,17 +16,20 @@ any personal data.
In addition, the following vendors offer free trial accounts for their Eclipse hawkBit compatible products:
-* [Bosch IoT Rollouts](https://bosch-iot-suite.com/service/rollouts/) (by [Bosch Digital](https://www.bosch-digital.com))
+* [Bosch IoT Rollouts](https://bosch-iot-suite.com/service/rollouts/) (
+ by [Bosch Digital](https://www.bosch-digital.com))
* [Kynetics Update Factory](https://www.kynetics.com/update-factory) (by [Kynetics LLC](https://www.kynetics.com/))
-
## From Docker Image
### Overview
-HawkBit Update Server username/password -> admin/admin as default login credentials. They can be overridden by the environment variables spring.security.user.name and spring.security.user.password which are defined in the corresponding default [application.properties](hawkbit-runtime/hawkbit-update-server/src/main/resources/application.properties).
+HawkBit Update Server username/password -> admin/admin as default login credentials. They can be overridden by the
+environment variables spring.security.user.name and spring.security.user.password which are defined in the corresponding
+default [application.properties](hawkbit-runtime/hawkbit-update-server/src/main/resources/application.properties).
It supports two configurations:
+
* monolith - hawkbit-update-server
* micro-service - hawkbit-mgmt-server, hawkbit-ddi-server, hawkbit-dmf-server.
@@ -61,6 +64,7 @@ $ docker-compose -f docker-compose-micro-service-mysql.yml up -d
## From Sources
### 1: Clone and build hawkBit
+
```sh
$ git clone https://github.com/eclipse-hawkbit/hawkbit.git
$ cd hawkbit
@@ -82,6 +86,7 @@ $ mvn clean install
```
### 4: Start hawkBit [Device Simulator](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-device-simulator)
+
```sh
$ java -jar ./hawkbit-device-simulator/target/hawkbit-device-simulator-#version#.jar
```
diff --git a/site/content/guides/clustering.md b/site/content/guides/clustering.md
index 4c21fdd79..d031d4c2a 100644
--- a/site/content/guides/clustering.md
+++ b/site/content/guides/clustering.md
@@ -4,7 +4,9 @@ parent: Guides
weight: 33
---
-hawkBit is able to run in a cluster with some constraints. This guide provides insights in the basic concepts and how to setup your own cluster. You can find additional information in the [hawkBit runtimes's README](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-runtime/hawkbit-update-server/README.md).
+hawkBit is able to run in a cluster with some constraints. This guide provides insights in the basic concepts and how to
+setup your own cluster. You can find additional information in
+the [hawkBit runtimes's README](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-runtime/hawkbit-update-server/README.md).
## Big picture
@@ -13,8 +15,13 @@ hawkBit is able to run in a cluster with some constraints. This guide provides i
## Events
-Event communication between nodes is based on [Spring Cloud Bus](https://cloud.spring.io/spring-cloud-bus/) and [Spring Cloud Stream](http://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/). There are different [binder implementations](http://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/#_binders) available. The _hawkbit Update Server_ uses RabbitMQ binder. Every node gets his own queue to receive cluster events, the default payload is JSON.
-If an event is thrown locally at one node, it will be automatically delivered to all other available nodes via the Spring Cloud Bus's topic exchange:
+Event communication between nodes is based on [Spring Cloud Bus](https://cloud.spring.io/spring-cloud-bus/)
+and [Spring Cloud Stream](http://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/). There are
+different [binder implementations](http://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/#_binders)
+available. The _hawkbit Update Server_ uses RabbitMQ binder. Every node gets his own queue to receive cluster events,
+the default payload is JSON.
+If an event is thrown locally at one node, it will be automatically delivered to all other available nodes via the
+Spring Cloud Bus's topic exchange:

@@ -23,16 +30,25 @@ Via the ServiceMatcher you can check whether an event happened locally at one no
## Caching
-Every node is maintaining its own caches independent from other nodes. So there is no globally shared/synchronized cache instance within the cluster. In order to keep nodes in sync a TTL (time to live) can be set for all caches to ensure that after some time the cache is refreshed from the database. To enable the TTL just set the property "hawkbit.cache.global.ttl" (value in milliseconds). Of course you can implement a shared cache, e.g. Redis.
+Every node is maintaining its own caches independent from other nodes. So there is no globally shared/synchronized cache
+instance within the cluster. In order to keep nodes in sync a TTL (time to live) can be set for all caches to ensure
+that after some time the cache is refreshed from the database. To enable the TTL just set the property "
+hawkbit.cache.global.ttl" (value in milliseconds). Of course you can implement a shared cache, e.g. Redis.
See [CacheAutoConfiguration](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-autoconfigure/src/main/java/org/eclipse/hawkbit/autoconfigure/cache/CacheAutoConfiguration.java)
## Schedulers
-Every node has multiple schedulers which run after a defined period of time. All schedulers always run on every node. This has to be kept in mind e.g. if the scheduler executes critical code which has to be executed only once.
+Every node has multiple schedulers which run after a defined period of time. All schedulers always run on every node.
+This has to be kept in mind e.g. if the scheduler executes critical code which has to be executed only once.
## Known constraints
### Denial-of-Service (DoS) filter
-hawkBit owns the feature of guarding itself from DoS attacks, a [DoS filter](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-http-security/src/main/java/org/eclipse/hawkbit/security/DosFilter.java). It reduces the maximum number of requests per seconds which can be configured for read and write requests.
-This mechanism is only working for every node separately, i.e. in a cluster environment the worst-case behaviour would be that the maximum number of requests per seconds will be increased to its product if every request is handled by a different node.
+
+hawkBit owns the feature of guarding itself from DoS attacks,
+a [DoS filter](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-http-security/src/main/java/org/eclipse/hawkbit/security/DosFilter.java).
+It reduces the maximum number of requests per seconds which can be configured for read and write requests.
+This mechanism is only working for every node separately, i.e. in a cluster environment the worst-case behaviour would
+be that the maximum number of requests per seconds will be increased to its product if every request is handled by a
+different node.
The same constraint exists with the validator to check if a user tried too many logins within a defined period of time.
diff --git a/site/content/guides/feignclient.md b/site/content/guides/feignclient.md
index 15102087d..10b3fd3a6 100644
--- a/site/content/guides/feignclient.md
+++ b/site/content/guides/feignclient.md
@@ -4,18 +4,31 @@ parent: Guides
weight: 32
---
-In this guide we describe how to create a [Feign](https://github.com/Netflix/feign) Rest Client based on a [Spring Boot](http://projects.spring.io/spring-boot/) Application.
+In this guide we describe how to create a [Feign](https://github.com/Netflix/feign) Rest Client based on
+a [Spring Boot](http://projects.spring.io/spring-boot/) Application.
## Create Feign REST Client
-hawkBit provides REST interfaces for [Management API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-ddi-api) and [DDI API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-ddi-api). Using this interfaces you can create a feign client with the help of the [feign inheritance support](http://projects.spring.io/spring-cloud/spring-cloud.html#spring-cloud-feign-inheritance).
-Our [example](https://github.com/eclipse-hawkbit/hawkbit-examples) modules demonstrate how to create [Feign](https://github.com/Netflix/feign) client resources. Here you can find the [Management API client resources](hhttps://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-mgmt-feign-client) and the [DDI client resources](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-ddi-feign-client).
-A small [simulator application](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-mgmt-simulator) demonstrates how you can interact with the hawkBit via the [Management API
-](http://www.eclipse.org/hawkbit/documentation/interfaces/management-api.html).
+
+hawkBit provides REST interfaces
+for [Management API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-ddi-api)
+and [DDI API](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkbit-ddi-api). Using this interfaces you can
+create a feign client with the help of
+the [feign inheritance support](http://projects.spring.io/spring-cloud/spring-cloud.html#spring-cloud-feign-inheritance).
+Our [example](https://github.com/eclipse-hawkbit/hawkbit-examples) modules demonstrate how to
+create [Feign](https://github.com/Netflix/feign) client resources. Here you can find
+the [Management API client resources](hhttps://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-mgmt-feign-client)
+and
+the [DDI client resources](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-ddi-feign-client).
+A
+small [simulator application](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-mgmt-simulator)
+demonstrates how you can interact with the hawkBit via the [Management API
+](http://www.eclipse.org/hawkbit/documentation/interfaces/management-api.html).
## Example Management API simulator
-In the follow code section, you can a see a feign client resource example. The interface extend the origin api interface to declare the `@FeignClient`. The `@FeignClient`declares that a REST client with that interface should be created.
+In the follow code section, you can a see a feign client resource example. The interface extend the origin api interface
+to declare the `@FeignClient`. The `@FeignClient`declares that a REST client with that interface should be created.
```Java
@FeignClient(url = "${hawkbit.url:localhost:8080}/" + MgmtRestConstants.TARGET_V1_REQUEST_MAPPING)
@@ -40,7 +53,8 @@ public class CreateStartedRolloutExample {
```
-At [hawkbit-example-core-feign-client](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-core-feign-client) is a spring configuration to auto configure some beans, which can be reused for a own feign client.
+At [hawkbit-example-core-feign-client](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-core-feign-client)
+is a spring configuration to auto configure some beans, which can be reused for a own feign client.
```Java
@Configuration
diff --git a/site/content/guides/runhawkbit.md b/site/content/guides/runhawkbit.md
index ecb0eac1e..70e5b897a 100644
--- a/site/content/guides/runhawkbit.md
+++ b/site/content/guides/runhawkbit.md
@@ -4,12 +4,14 @@ parent: Guides
weight: 31
---
-In this guide we describe how to run a full featured hawkBit setup based on a production ready infrastructure. It is based on the hawkBit example modules and update server.
+In this guide we describe how to run a full featured hawkBit setup based on a production ready infrastructure. It is
+based on the hawkBit example modules and update server.
{{% note %}}
-The update server can in fact be run stand alone. However, only with an embedded H2, no Device Management Federation API and no artifact storage.
+The update server can in fact be run stand alone. However, only with an embedded H2, no Device Management Federation API
+and no artifact storage.
{{% /note %}}
## System Architecture
@@ -30,7 +32,8 @@ This guide describes a target architecture that is more like one that you will e
## Adapt hawkBit Update Server and Device Simulator to your environment.
-As mentioned you can create your own application with hawkBit inside or adapt the existing example app. The second option will be shown here.
+As mentioned you can create your own application with hawkBit inside or adapt the existing example app. The second
+option will be shown here.
### Set MariaDB dependency to compile in the [update server POM](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-runtime/hawkbit-update-server/pom.xml)
@@ -44,7 +47,8 @@ As mentioned you can create your own application with hawkBit inside or adapt th
### Configure MariaDB/MySQL connection settings.
-For this you can either edit the existing _application.properties_ or create a [new profile](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#boot-features-external-config-profile-specific-properties).
+For this you can either edit the existing _application.properties_ or create
+a [new profile](http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#boot-features-external-config-profile-specific-properties).
```properties
spring.jpa.database=MYSQL
@@ -54,12 +58,15 @@ spring.datasource.password=YOUR_PWD
spring.datasource.driverClassName=org.mariadb.jdbc.Driver
```
-Note: On Ubuntu 18.04 with MariaDB 10.1 installed from the default repository via apt install _COLLATE option_ of database have to be changed manually to "latin1".
-For recent versions of MariaDB running on Ubuntu this is not required (cf. [system variables](https://mariadb.com/kb/en/differences-in-mariadb-in-debian-and-ubuntu), [issue](https://github.com/eclipse-hawkbit/hawkbit/issues/963))
+Note: On Ubuntu 18.04 with MariaDB 10.1 installed from the default repository via apt install _COLLATE option_ of
+database have to be changed manually to "latin1".
+For recent versions of MariaDB running on Ubuntu this is not required (
+cf. [system variables](https://mariadb.com/kb/en/differences-in-mariadb-in-debian-and-ubuntu), [issue](https://github.com/eclipse-hawkbit/hawkbit/issues/963))
### Configure RabbitMQ connection settings for update server and device simulator (optional).
-We provide already defaults that should work with a standard Rabbit installation. Otherwise configure the following in the `application.properties` of the two services:
+We provide already defaults that should work with a standard Rabbit installation. Otherwise configure the following in
+the `application.properties` of the two services:
```properties
spring.rabbitmq.username=guest
@@ -93,9 +100,11 @@ see [update server](https://github.com/eclipse-hawkbit/hawkbit/tree/master/hawkb
### Compile & Run example scenario [creation script](https://github.com/eclipse-hawkbit/hawkbit-examples/tree/master/hawkbit-example-mgmt-simulator) (optional)
-This has to be done before the device simulator is started. hawkBit creates the mandatory tenant metadata with first login into either Management API (which is done by this client).
+This has to be done before the device simulator is started. hawkBit creates the mandatory tenant metadata with first
+login into either Management API (which is done by this client).
-However, this is not done by _DMF_ which is in fact used by the device simulator, i.e. without calling _Management API_ first hawkBit would drop all _DMF_ messages as the tenant is unknown.
+However, this is not done by _DMF_ which is in fact used by the device simulator, i.e. without calling _Management API_
+first hawkBit would drop all _DMF_ messages as the tenant is unknown.
### Compile & Run device simulator (optional)
diff --git a/site/content/release-notes.md b/site/content/release-notes.md
index 2971b25aa..89ca1ccb8 100755
--- a/site/content/release-notes.md
+++ b/site/content/release-notes.md
@@ -28,25 +28,24 @@ Extensions: [Tag](https://github.com/eclipse-hawkbit/hawkbit-extensions/releases
**Release Date:** Thursday, August 24, 2023
Hawkbit: [Tag](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.3.0M9) /
- [Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/24)
+[Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/24)
Extensions: [Tag](https://github.com/eclipse-hawkbit/hawkbit-extensions/releases/tag/0.3.0M9)
## 0.3.0M8
**Release Date:** Friday, April 21, 2023
Hawkbit: [Tag](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.3.0M8) /
- [Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/23)
+[Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/23)
Extensions: [Tag](https://github.com/eclipse-hawkbit/hawkbit-extensions/releases/tag/0.3.0M8) /
- [Release](https://github.com/eclipse-hawkbit/hawkbit-extensions/milestone/2)
-
+[Release](https://github.com/eclipse-hawkbit/hawkbit-extensions/milestone/2)
## 0.3.0M7
**Release Date:** Monday, February 15, 2021
Hawkbit: [Tag](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.3.0M7) /
- [Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/22?closed=1)
+[Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/22?closed=1)
Extensions: [Tag](https://github.com/eclipse-hawkbit/hawkbit-extensions/releases/tag/0.3.0M7) /
- [Release](https://github.com/eclipse-hawkbit/hawkbit-extensions/milestone/1?closed=1)
+[Release](https://github.com/eclipse-hawkbit/hawkbit-extensions/milestone/1?closed=1)
## 0.3.0M6
@@ -114,20 +113,19 @@ Extensions: [Tag](https://github.com/eclipse-hawkbit/hawkbit-extensions/releases
[Tag](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.2.1) /
[Release](https://github.com/eclipse-hawkbit/hawkbit/milestone/9?closed=1)
-
## 0.2.0
First Eclipse hawkBit release including:
* **Core features:**
- * Device and Software Repository
- * Artifact Content Delivery
- * Rollout/Campaign Management
+ * Device and Software Repository
+ * Artifact Content Delivery
+ * Rollout/Campaign Management
* **Interfaces:**
- * Management API
- * Direct Device Integration (DDI) API
- * Device Management Federation (DMF) API
+ * Management API
+ * Direct Device Integration (DDI) API
+ * Device Management Federation (DMF) API
**Release Date:** Friday, June 15, 2018
[Tag](https://github.com/eclipse-hawkbit/hawkbit/releases/tag/0.2.0) /
diff --git a/site/content/whatishawkbit.md b/site/content/whatishawkbit.md
index c1b091fdb..6d96d8ed6 100755
--- a/site/content/whatishawkbit.md
+++ b/site/content/whatishawkbit.md
@@ -2,37 +2,73 @@
title: What is hawkBit?
weight: 10
---
-Eclipse hawkBit™ is a domain-independent back-end framework for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.
+
+Eclipse hawkBit™ is a domain-independent back-end framework for rolling out software updates to constrained edge
+devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.

## Why Software Updates in IoT?
-Having software update capabilities ensures a secure IoT by means that it gives IoT projects a fighting chance against pandora's box that they opened the moment their devices got connected. From that moment on devices are at the forefront of IT security threats many embedded software developers historically never had to face. Shipping for instance a Linux powered device connected to the Internet without any security updates ever applied during its lifetime is kind of a suicidal act these days.
-A more charming argument for software update is that it enables agile development for hardware and hardware near development. Concepts like a minimum viable product can be applied for devices as not all features need to be ready at manufacturing time. Changes on the cloud side of the IoT project can be applied to the devices at runtime as well.
+Having software update capabilities ensures a secure IoT by means that it gives IoT projects a fighting chance against
+pandora's box that they opened the moment their devices got connected. From that moment on devices are at the forefront
+of IT security threats many embedded software developers historically never had to face. Shipping for instance a Linux
+powered device connected to the Internet without any security updates ever applied during its lifetime is kind of a
+suicidal act these days.
-Sometimes Software Update is a business model on its own as it makes devices much more attractive to the customer if they are updatable, i.e. they do not only buy a product because of its current feature set but make also a bet on its future capabilities. In addition new revenue streams may arise from the fact that feature extensions can potentially be monetized (e.g. Apps) without the need to design, manufacture and ship a new device (revision).
+A more charming argument for software update is that it enables agile development for hardware and hardware near
+development. Concepts like a minimum viable product can be applied for devices as not all features need to be ready at
+manufacturing time. Changes on the cloud side of the IoT project can be applied to the devices at runtime as well.
+
+Sometimes Software Update is a business model on its own as it makes devices much more attractive to the customer if
+they are updatable, i.e. they do not only buy a product because of its current feature set but make also a bet on its
+future capabilities. In addition new revenue streams may arise from the fact that feature extensions can potentially be
+monetized (e.g. Apps) without the need to design, manufacture and ship a new device (revision).
## Why hawkBit?
-**Updating software** (components) on constrained edge devices as well as more powerful controllers and gateways is as mentioned before a **common requirement** in most IoT scenarios.
+**Updating software** (components) on constrained edge devices as well as more powerful controllers and gateways is as
+mentioned before a **common requirement** in most IoT scenarios.
-At the time being, this process is **usually handled by the IoT solution itself**, sometimes backed by a full fledged device management system. We believe that this approach generates unnecessary **duplicate work** in the IoT space, in particular when considering the challenges of implementing a safe and reliable remote software update process: the software update process must never fail and also must never be compromised as, at the one hand, it can be used to fix almost any issue/problem on the device but at the same time also poses the greatest security threat if mis-used to introduce malicious code to the device.
+At the time being, this process is **usually handled by the IoT solution itself**, sometimes backed by a full fledged
+device management system. We believe that this approach generates unnecessary **duplicate work** in the IoT space, in
+particular when considering the challenges of implementing a safe and reliable remote software update process: the
+software update process must never fail and also must never be compromised as, at the one hand, it can be used to fix
+almost any issue/problem on the device but at the same time also poses the greatest security threat if mis-used to
+introduce malicious code to the device.
-In addition we believe the software update process to be relatively **independent from particular application domains** when seen from the back-end (cloud) perspective. Updating the software for an entire car may differ from updating the firmware of a single sensor with regard to the connectivity of the device to the cloud and also to the complexity of the software package update process on the device. However, the process of rolling out the software, e.g. uploading an artifact to the repository, assigning it to eligible devices, managing the roll out campaign for a large number of devices, orchestrating content delivery networks to distribute the package, monitoring and reporting the progress of the roll-out and last but not least requirements regarding security and reliability are quite similar.
+In addition we believe the software update process to be relatively **independent from particular application domains**
+when seen from the back-end (cloud) perspective. Updating the software for an entire car may differ from updating the
+firmware of a single sensor with regard to the connectivity of the device to the cloud and also to the complexity of the
+software package update process on the device. However, the process of rolling out the software, e.g. uploading an
+artifact to the repository, assigning it to eligible devices, managing the roll out campaign for a large number of
+devices, orchestrating content delivery networks to distribute the package, monitoring and reporting the progress of the
+roll-out and last but not least requirements regarding security and reliability are quite similar.
-Software update itself is often seen as a sub process of general device management. In fact, most device management systems include functionality for triggering groups of devices to perform an update, usually accompanied by an artifact repository and basic reporting and monitoring capabilities. This is true for both systems specifically targeting IoT as well as systems originating from the mobile area.
+Software update itself is often seen as a sub process of general device management. In fact, most device management
+systems include functionality for triggering groups of devices to perform an update, usually accompanied by an artifact
+repository and basic reporting and monitoring capabilities. This is true for both systems specifically targeting IoT as
+well as systems originating from the mobile area.
-Existing **device management systems** usually **lack** the capability to **efficiently organize roll outs at IoT scale**, e.g. splitting the roll out into sub groups, cascading them, automatically stopping the roll out after a defined error threshold etc. They are also usually restricted to a single device management protocol, either a proprietary one or one of the existing standard protocols like LWM2M, OMA-DM or TR-069. Even if they support more than one such protocol, they are often a result of the device management protocol they started with and restricted in their adoption capabilities to others.
+Existing **device management systems** usually **lack** the capability to **efficiently organize roll outs at IoT scale
+**, e.g. splitting the roll out into sub groups, cascading them, automatically stopping the roll out after a defined
+error threshold etc. They are also usually restricted to a single device management protocol, either a proprietary one
+or one of the existing standard protocols like LWM2M, OMA-DM or TR-069. Even if they support more than one such
+protocol, they are often a result of the device management protocol they started with and restricted in their adoption
+capabilities to others.
-At the same time the wide functional scope of a full fledged **device management system introduces unnecessary (and unwanted) complexity** to many IoT projects. This is particularly true for IoT solutions working with constrained devices where requirements regarding generic device management are often very limited only but a secure & reliable software update process is still mandatory.
+At the same time the wide functional scope of a full fledged **device management system introduces unnecessary (and
+unwanted) complexity** to many IoT projects. This is particularly true for IoT solutions working with constrained
+devices where requirements regarding generic device management are often very limited only but a secure & reliable
+software update process is still mandatory.
As a result we have the need for a domain independent solution
-* that works for the majority of IoT projects
-* that goes beyond the pure update and handles more complex **roll out strategies** needed by large scale IoT projects.
-* that at the same time is **focused on software updates** in the IoT space
-* and that is able to work on its own for simple scenarios while having the capability to integrate with existing device management systems and protocols.
+* that works for the majority of IoT projects
+* that goes beyond the pure update and handles more complex **roll out strategies** needed by large scale IoT projects.
+* that at the same time is **focused on software updates** in the IoT space
+* and that is able to work on its own for simple scenarios while having the capability to integrate with existing device
+ management systems and protocols.
## Cloud Ready
@@ -40,4 +76,5 @@ As a result we have the need for a domain independent solution
* **Functional Scalability**: rollouts with hundreds of thousands of individual devices in it.
* **Reliability**: software update as the last line of defense against device faults and vulnerabilities.
* **Managed device complexity**: device topologies inside each individual provisioning target.
-* **Integration flexibility**: connect and integrate through various (non-)standardized device management protocols directly or through federated device managements.
\ No newline at end of file
+* **Integration flexibility**: connect and integrate through various (non-)standardized device management protocols
+ directly or through federated device managements.
\ No newline at end of file
diff --git a/site/layouts/_default/list.html b/site/layouts/_default/list.html
index cbaeb5f78..da0db6041 100755
--- a/site/layouts/_default/list.html
+++ b/site/layouts/_default/list.html
@@ -1,54 +1,54 @@
{{ partial "head" . }}
{{ if (eq (trim .Site.Params.provider " " | lower) "github") | and (isset .Site.Params "repo_url") }}
- {{ $repo_id := replace .Site.Params.repo_url "https://github.com/" ""}}
- {{ .Scratch.Set "repo_id" $repo_id }}
+{{ $repo_id := replace .Site.Params.repo_url "https://github.com/" ""}}
+{{ .Scratch.Set "repo_id" $repo_id }}
{{ end }}