vRA 8 – XaaS Blueprints and Deployment Objects

This post was originally published on this site

In 7.x versions of vRA you could have an XaaS blueprint that just executed a simple orchestrator task and upon completion it didn’t leave anything behind.  In my testing with 8.x it seems like XaaS blueprints leave behind a deployment object with workflow ID, run ID, etc.  Is there a way to turn this off and have it not leave behind a deployment object?  It seems like it’s just leaving behind a mess as the deployment doesn’t really have any options.  I get the logging in it could be beneficial to an admin, but to an end user I think it’s just clutter.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.