Each plugin will require one or more properties to connect to, or manage, the implementation of a build or deployment operation specific to the underlying platform or technology. Each plugin operation provides the definition of properties it requires, and specifies the scope where it makes the most sense to manage. When a plugin operation is associated to an instance, FlexDeploy understands that all of its properties must be available for configuration on the environment instance (for environment instance scoped properties) or on all projects (for project scoped properties) which use those instances.
It is important to understand that it is the plugin provider that determines which properties, whether optional or required, are exposed through its implementation. The FlexDeploy user who configures the topology and/or projects is then responsible for configuring values for those properties.