This repository has been archived by the owner on Jul 11, 2022. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BZ 958922] RFE: support for passing plugin config when creating child
resources Now we support all 4 possible 'ways' to create a resource on RHQ 1. regular resource (was already implemented) - when REST client create resources that agent would have discovered. Such resources is not possible to create via UI or CLI 2. content-based resources (was already implemented) 3. resource children: similar to content-based resources, UI analogy is "Create Child". Create child history exists. - possible resource duplicities are handled on agent side. 4. manual resources: Resources that could be only manually Imported from UI, create child history does not exist for those, and their resource key highly depends on given pluginConfiguration (although resourceName can be passed). Duplicates are handled on server side, since underlying API does not report an error when manually imported resource already exists. For 3. and 4. there's client can optinaly pass only required plugin/resource configurations. In rest api code, we retrieve all the defaults from resource type and then apply passed values on top.
- Loading branch information
Libor Zoubek
committed
Mar 18, 2014
1 parent
65e78e6
commit 69439e8
Showing
4 changed files
with
499 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.