Skip to content

Conversation

@ahgittin
Copy link
Contributor

previously template was the only way to class something as an application, and it did both:

  • generate a spec for an Application
  • add the catalog_template tag so it looks llke a template

this adds support for an itemType: application which only does the first of these

prevents delays while it tries to resolve things which aren't immediately available
@ahgittin ahgittin force-pushed the catalog-itemtype-application branch from 4100f9b to 5dbf70d Compare November 15, 2018 17:59
@ahgittin
Copy link
Contributor Author

also fixes issue with resolving details for things which aren't immediately available, in first commit here

Copy link
Member

@grkvlt grkvlt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@asfgit asfgit merged commit 5dbf70d into apache:master Nov 15, 2018
asfgit pushed a commit that referenced this pull request Nov 15, 2018
* origin/pr/1015:
  introduce new distinct "application" itemType on catalog BOM files, which don't set template tag
  when getting details, get the raw value then resolve it immediately
ahgittin added a commit to ahgittin/brooklyn-ui that referenced this pull request Nov 16, 2018
in line with apache/brooklyn-server#1015
also when using a template the metadata is not populated as the intention is probably not to overwrite,
unless the user selects to save it as a template
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

Successfully merging this pull request may close these issues.

3 participants