[OPENAM-16001] Configuration Import of External Data Store Created: 09/Mar/20  Updated: 11/Mar/20

Status: Open
Project: OpenAM
Component/s: Amster, configurator
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Jobby Thomas Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: CustomerRFE, DATASTORE, configuration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Rank: 1|i005sv:
Support Ticket IDs:

 Description   

issue background:

Certain AM Configurations must be imported in order

 

While working to separate application configuration in a separate store from our CFG config, customer noticed that some of the configuration needed to be imported (via amster) in an exact order while the documentation does not call that out.

Customer had to import in order:

  • all global configs
  • top realm DataStoreInstance config
  • top realm DataStoreService config
  • all other Realm configs
  • sub-Realm specific DataStoreService configs
  • Realm Applications

 

RFE request: 

It would be preferable to not need to import configurations in specific order or have documentation on different configuration dependencies. Customer solution added some complexity to our deployment/build scripts as well as our repository

 



 Comments   
Comment by Andy Hall [ 11/Mar/20 ]

AMster has an ordering already, could be we need to update the dependency chain.

Comment by Peter Major [X] (Inactive) [ 11/Mar/20 ]

Sounds more like a bug then..

Generated at Mon Mar 01 10:51:27 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.