Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic Updates to SolutionTemplates #2241

Open
ysknkd opened this issue Jul 18, 2023 · 0 comments
Open

Dynamic Updates to SolutionTemplates #2241

ysknkd opened this issue Jul 18, 2023 · 0 comments

Comments

@ysknkd
Copy link
Contributor

ysknkd commented Jul 18, 2023

SolutionTemplates are very useful, but the current requirement for a deployment when adding a new template introduces a lead time from when a user requests an addition to when it is deployed. I was wondering if there are any plans or considerations for enabling Solution Templates to be dynamically updated in the future. Do you have any plans for this?

void loadSolutionTemplates() {
// get the configured path for the list of service templates
String solutionTemplatesFname = System.getProperty(ZMSConsts.ZMS_PROP_SOLUTION_TEMPLATE_FNAME,
getRootDir() + "/conf/zms_server/solution_templates.json");
Path path = Paths.get(solutionTemplatesFname);
try {
serverSolutionTemplates = JSON.fromBytes(Files.readAllBytes(path), SolutionTemplates.class);
} catch (IOException ex) {
LOG.error("Unable to parse solution templates file {}: {}",
solutionTemplatesFname, ex.getMessage());
}
if (serverSolutionTemplates == null) {
LOG.error("Generating empty solution template list...");
serverSolutionTemplates = new SolutionTemplates();
serverSolutionTemplates.setTemplates(new HashMap<>());
serverSolutionTemplateNames = Collections.emptyList();
} else {
serverSolutionTemplateNames = new ArrayList<>(serverSolutionTemplates.names());
Collections.sort(serverSolutionTemplateNames);
}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant