In this blog post we are going to look at how to use Blueprint Options in Cloud Assembly to extend ABX extensibility.
Update Log:
Introduction
Subscriptions in Cloud Assembly let you subscribe an extensibility action to a particular Event Type so that the action is only triggered for that event type. In addition, subscriptions offer Event Typic Condition Filtering which lets you filter even more when an action should be triggered. For example you can use event.data.zoneId filter to trigger the subscribed action only if a particular zone was selected for deployment. Condition filtering is great and adds a lot of flexibility.
Blueprint Options can further exchange an enrich the extensibility options, by allowing you to enable or disable particular ABX actins to run from within the blueprint. For example in one of my previous posts spoke a bout an ABX action which I created which syncs blueprint versions to Gitlab. Now if I want that action to run only for particular blueprints I can enable the corresponding Blueprint Option from within each blueprint.
Blueprint Options
Here are the currently supported Blueprint Options:
- GItlab
- gitlabSyncEnable (Boolean)
- True: Enables Gitlab synchronization
- False: Disables Gitlab synchronization
- gitlabSyncDelete (Boolean)
- True: If blueprint is deleted from Assembly, it will be deleted in git.
- False: If a blueprint is deleted from Assembly, it will not be deleted in git.
- Slack
- slackPostEnable
- True: Enables Slack Notification
- False: Disables Slack Notification
- AWS Simple Email Service (SES)
- awsSesEmailEnable
- True: Enables Email Notification
- False: Disables Email Notification
These Blueprint Options are set via level properties in the blueprint yaml. Here again an example of the supported Blueprint Options in the blueprint yaml:
[sourcecode language=”yaml”]
#——————————————————–#
# Spas Kaloferov #
# www.kaloferov.com #
# bit.ly/The-Twitter Social bit.ly/The-LinkedIn #
# bit.ly/The-Gitlab Git bit.ly/The-Github #
# bit.ly/The-BSD License bit.ly/The-GNU #
#——————————————————–#
info: |-
#
# VMware Cloud Assembly Blueprint Code Sample
#
name: Blueprint Options
version: 1
options:
gitlabSyncEnable: True
gitlabSyncDelete: false
awsSesEmailEnable: True
slackPostEnable: false
inputs: {}
resources: {}
[/sourcecode]
More on this and how to use the Blueprint Options in general can be found here: ABX Action to Sync Blueprints from Assembly to Gitlab (SKKB1050)
The actions can be found on bit.ly/The-Gitlab.
Here directly download links:
Integration |
ABX Action |
Requires |
Sample Exchange |
Gitlab |
Gitlab |
casSyncBlueprintToGitlab |
v1 |
||
Slack |
slackPost |
v2 |
||
AWS SES |
awsSesSendEmail |
v2 |
Final Step
If all went well, go grab a beer.
include_once TEMPLATEPATH."/../../../itBlogDisclaimer.php"; ?>