You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/01/20 23:08:35 UTC
[jira] [Created] (AMBARI-9223) Add properties_attributes support to
exported Blueprints
Robert Nettleton created AMBARI-9223:
----------------------------------------
Summary: Add properties_attributes support to exported Blueprints
Key: AMBARI-9223
URL: https://issues.apache.org/jira/browse/AMBARI-9223
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Fix For: 2.0.0
Attributes of configuration properties are not properly included when a Blueprint is exported from a running cluster.
To reproduce:
1. Start a cluster with the Ambari UI, mark some configuration properties as "final".
2. After the cluster has successfully started, use the Blueprint REST API to export a Blueprint based on this running cluster.
3. The configuration elements in the exported Blueprint will not include the proper metadata about a configuration property. In this specific case, the Blueprint will not indicate which configuration elements are "final".
This is only a bug in the Blueprint cluster renderer, as most of the support for "properties_attributes" already exists in the BlueprintResourceProvider and ClusterResourceProvider.
The ClusterBlueprintRenderer class needs to be updated to pull out the properties_attributes from the Cluster resource, and include these within the "configurations" map of the exported Blueprint.
I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)