You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `apiPath` | The relative path of the API on the endpoint | | `v1/Resource/ApiResource`
89
89
| `typeDescription` | Description of the subresource
90
-
| `identifierQueryParam` | Some APIs handle deletion of entities by DELETEing the parent resource and specifying the entity to delete in a query parameter. If the subresource handles DELETEion in that way, the query parameter to use for identifying the object needs to be stated here. If empty or unspecified, DELETE calls will be made to the path which ends with the entities name. || `"Guid"`
90
+
| `identifierQueryParam` | Some APIs handle deletion of entities by DELETEing the parent resource and specifying the entity to delete in a query parameter. If the subresource handles DELETEion in that way, the query parameter to use for identifying the object needs to be stated here. If empty or unspecified, DELETE calls will be made to the path which ends with the entities identifier. NOTE: This setting usually needs entity setting 'deleteUriExcludeIdentifier' to be true as well! || `"Guid"`
91
91
| `stage` | Stage where this `subresource` is processed. Overwrites `stage` from `endpoint` level. <br>All subresources are by default processed during execution of the `hull-install` job by setting stage `pre-install` before installation of the main product of the parent Helm Chart. If you for example need to communicate to the API of a product you just installed within the parents Helm chart, set the `stage` to `post-install` and the processing takes places within the `hull-configure` job after the main product installation is done. | `pre-install` | `post-install`
92
92
| `auth` | Allows to override the `endpoint`s `auth` configuration at the `subresource` scope<br><br>Has one of following keys:<br>`basic`<br>`token`
93
93
| `_DEFAULTS_` | Defaults for all `entity` objects defined under this `endpoint`. Can be used to set all `entity` properties to a default value. Technically all `entity` values will be merged on top of the `_DEFAULTS_` | | `_DEFAULTS_:`<br>  `register:` `true`<br>  `overwriteExisting:` `false`
@@ -99,8 +99,9 @@ Describes a particular entity on a subresource on an endpoint which is communica
| `register` | If set to true, the entity will be created or modified |
102
-
| `remove` | The entity will be DELETEd if it exists
103
-
| `identifier` | Optional field to specify the objects 'identifier', if not set or empty the object 'identifier' will be set to the key of the entity. The identifier is important for making a standard GET call to determine if the entity already exists, it provides the last part of the GET uri, for example `https://host.com/API/notifications/groups/NOTIFICATION-VX-99`. <br><br>Note that this setting is irrelevant if either `noGet` or `getUriExcludeIndentifier` are set to `true`.<br><br>A typical usecase for this is having an object being identified by a GUID but wanting to use a more speaking name for the entity key or utilize the ordering via suitable key names instead of using a non-speaking GUID.' |
102
+
| `remove` | The entity will be DELETEd if it exists. If both `register` and `remove` is true, any found entity is first removed if it exists before it is being created.
103
+
| `identifier` | Optional field to specify the objects 'identifier', if not set or empty the object 'identifier' will be set to the key of the entity. The identifier is important for making a standard GET call to determine if the entity already exists, it provides the last part of the GET uri, for example `https://host.com/API/notifications/groups/NOTIFICATION-VX-99`. <br><br>Note that this setting is irrelevant if either `noGet` or `getUriExcludeIndentifier` are set to `true`.<br><br>A typical usecase for this is having an object being identified by a GUID but wanting to use a more speaking name for the entity key or utilize the ordering via suitable key names instead of using a non-speaking GUID.' |
104
+
| `deleteUriExcludeIdentifier` | Some APIs handle DELETEing of entities by calling DELETE to the parent resource and specifying the entity to delete in query params. If the subresource handles DELETEing in that way, set this parameter to `true` and provide the subresource `identifierQueryParam` to identify the entity. If `false` or unspecified, DELETE calls will be made to the path which ends with the entities identifier name.
104
105
| `putUriExcludeIdentifier` | Some APIs handle PUTting of entities by PUTing to the parent resource and specifying the entity to create in the body. If the subresource handles PUTting in that way, set this parameter to `true`. If `false` or unspecified, PUT calls will be made to the path which ends with the entities name.
105
106
| `putInsteadOfPost` | Some APIs use PUTting instead of POSTing for creation of new entities. If the subresource uses PUTting instead of POSTing, set this parameter to `true`.
106
107
| `postQueryParams` | Query Parameters to add to the Url of a POST command. Not a frequent usa case but required to submit for example the `guid` of a UseCaseDefinition to migrate.
0 commit comments