Addressing some of the recent created Issues (#2891)

* Add missing open api schema for Creation of DistributionSet #2745
* Fixed Target Security Token lenght in doc - possible max value 128 chars
* Re-visit Security token doc

---------
Signed-off-by: vasilchev <vasil.ilchev@bosch.com>
This commit is contained in:
Vasil Ilchev
2026-01-27 11:12:48 +02:00
committed by GitHub
parent 41e4f94c17
commit 69840310e7
2 changed files with 15 additions and 2 deletions

View File

@@ -18,8 +18,9 @@ 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_.
If not set by the user, the security token is automatically generated with 32 alphanumeric characters.
However, the user can provide a custom token with a maximum length of 128 alphanumeric characters.
This token can be used to authenticate the target at hawkBit through the HTTP-Authorization Header with the custom scheme _TargetToken_.
```http
GET /DEFAULT/controller/v1/0e945f95-9117-4500-9b0a-9c6d72fa6c07 HTTP/1.1

View File

@@ -32,6 +32,18 @@ import org.eclipse.hawkbit.mgmt.json.model.softwaremodule.MgmtSoftwareModuleAssi
@JsonIgnoreProperties(ignoreUnknown = true)
public class MgmtDistributionSetRequestBodyPost extends MgmtDistributionSetRequestBodyPut {
@Schema(description = "Array of Software Modules assigned to the distribution set. " +
"Software Modules assigned to Distribution Set would define the 'complete' property of DistributionSet." +
"Assigned Software Modules must be 'complete' in order DistributionSet to be 'complete'." +
"Distribution Sets that are not 'complete' cannot be used in a Rollout/Auto-Assignment", example = """
[
{
"id": 1
},
{
"id": 2
}
]""")
private List<MgmtSoftwareModuleAssignment> modules;
@Schema(description = "The type of the distribution set", example = "test_default_ds_type")