I like `requiredInstancesPerEnvironment`. I just committed the refactoring to 'mustBeMapped' but this feels better. Hold on .. :-)
BTW I think `minNumInstances` and `maxNumInstances` is too low level. Abstracting to 0-1-n is clearer imho.

________________________________
Van: Andrew Phillips [notifications@github.com]
Verzonden: dinsdag 8 oktober 2013 11:35
Aan: xebialabs/community-plugins
CC: Bastiaan Bakker
Onderwerp: Re: [community-plugins] Feature deployment complete validator (#42)


In deployit-udm-plugins/utility-plugins/deployment-complete-validator-plugin/README.md:

> +# Overview #
> +
> +The Deployment Complete Validator plugin is a Deployit plugin that enables automatic enforcement of completeness of deployments. If a deployment does not include
> +all required deployed the deployment will not proceed.
> +
> +# Requirements #
> +
> +* **Deployit**: tested with Deployit 3.9.3, your mileage may vary with older releases.
> +
> +# Installation #
> +
> +Place the plugin JAR file into your `SERVER_HOME/plugins` directory.
> +
> +# Usage
> +
> +This plugin adds the optional property `deploymentCardinality` to `udm.Deployable`. This is an enum that specifies how many Deployeds the deployment should generate for


is more about restricting HOW a deployable should be mapped whereas mustBeMapped

I see your point about mR - the thing about mustBeMapped to me is that it sounds like a boolean. mappingStrategy? mappingModel?

Or, changing themes again, requiredInstancesPerEnvironment? requiredMappingsPerEnv? With values NONE, AT_MOST_ONE, ..?

In fact, in that case you could make the model a little easier and simply expose two properties: minNumInstances and (optionally) maxNumInstances (integers >= 0) and use those?

—
Reply to this email directly or view it on GitHub<https://github.com/xebialabs/community-plugins/pull/42/files#r6820786>.