A deployment is the way that the seedata.io platform ‘plants’ and ‘retires’ your seeds. They are the automated specification for how you want a particular set of seeds to be constructed, and instructions on where you would like them to be placed and how long they should live there for. The following sections describe all steps required to get your deployments buzzing!
Create a new deployment
You would need to create a new deployment if you want plant any type of seed in any location. This includes seeds created for manual downloading.
From the left menu, click on Deployments
In the top right of this page, you click on a button to Add New
This will open a new window with a form the requires completion
There’s a few terms used on this form that will be useful to have a common understanding of.
Seed type
We offer a range of different seed types that suit different purposes and use cases. More details on when and how to use each specific type are available in the support pages, and several use-cases are explored within our website and on our blog. This field is mandatory.
Destination
This informs us where you ultimately want to put the seeds. You have the following choices:
Manual Download – Some seed types are only suitable for manual download, so this will be the only option available to you. This is because they require additional configuration in order to work (such as our DNS Redirect seeds). In such cases, when you run the deployment, we will create the seed and make it available to you for downloading
An existing integration – you may have already created an integration (see here for more information on this). If the seed type supports it, you can choose for seedata.io to automatically plant and retire seeds using this destination. If the integration type supports it, the seedata.io platform will offer further configurations such as which folders to write to.
Seed impact
Risk is about impact and likelihood, so here is where we record the potential impact to you if a seed is activated in any way, based upon the location you are planting the seed into. You might choose a low impact for those deployments that will plant seeds on the perimeter of your network (or beyond), because you expect they will get activated frequently, whereas seeds placed in your director’s personal workstation should never get activated so would warrant a very high impact rating. We use this to help assign the priority of any events we raise to you.
Seed lifespan
You may choose to plant a seed and leave it in place indefinitely (so leave this set to “No Expiry”), or you may prefer to cycle your seeds on a regular frequency (say, each seed gets swapped after being in place for 7 days). Be aware that you cant automatically expire seeds set to manually download (because we can’t reach them to retire and plant new ones). Different values suit different seed types and different situations, and these are covered in more detail elsewhere, but you’ll not go wrong with anything between 7 days to 90 days.
Deployment size
This dictates how many seeds of this description should be running as ‘planted’ at the same time. The deployment will automatically calculate how often it must run to maintain your chosen deployment size and your desired seed lifespan, then plant and retire seeds accordingly. It’s important to note that deployments set to manually download will create their full deployment size every time they are run.
Mute notifications
This toggle configures whether you would like email updates to confirm success/failure of the deployment operations (such as create new seed, plant or retire seeds). All notifications go to the user that created the deployment.
Run on save
You can create a deployment to be used later, or you can have the deployment run immediately
Once completed, you should push Save (or cancel if you’ve changed your mind).
This will create a new row in list of all saved deployments. If you set your deployment to “Run on save”, you will see the deployment is first set with a status of “initialising”. This indicates the deployment is creating the first set of seeds to fulfil your desired deployment size.
Run an previously created deployment
if you created a deployment and chose not to set “Run on save”, or you stopped a previously running deployment, you will need to manually run the deployment. Click the actions menu (three dots in a box, on the right side of each row) for the deployment you are interested in, then click Run.
Once launched, you will see the status change to Running, and your seeds will be created
Viewing details for an existing deployment
Clicking on any individual row in the deployments table will take you through to a detailed view of that specific deployment, listing details of all seeds created by that deployment.
Delete an existing deployment
If you want to permanently remove the deployment, click on the actions menu on the right of the row, then click Delete
A new dialog will appear, asking you to confirm this action, or cancel it.
Once you confirm, the deployment will be deleted. No future planting or retiring activity will be instructed, and any seeds previously created by it will require manual management
Mute / Unmute deployment notifications
For some deployment, you may not want to receive notifications of each and every interaction. In such cases, you can simply mute (or unmute, if you’ve changed your mind) the notifications.
Click on the actions menu to the right side of the row, and click mute/unmute (note, you will only see the option that changes from the current state)
Once clicked, you will see either the addition or removal of a Mute icon next to the deployment name
