You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a DeploymentPackager is called there is knowledge of the target DeployableContainer
and a ProtocolDefinition which contains the default protocol configuration. This is not provided to the DeploymentPackager via the DeploymentDescription available from the TestDeployment argument to DeploymentPackager#generateDeployment()..
The DeployableContainer is also capable of overriding the protocol and configuration, so that value is what needs to be first looked at, and then fallback to the default ProtocolDefinition if none was specified at the container level. This needs
to be specified on the TestDeployment.
Expected Behaviour
The TestDeployment should have the target protocol information available.
Current Behaviour
This information, while available at the time the DeploymentPackager is called, is not provided via the TestDeployment argument.
The text was updated successfully, but these errors were encountered:
Issue Overview
When a
DeploymentPackager
is called there is knowledge of the targetDeployableContainer
and a
ProtocolDefinition
which contains the default protocol configuration. This is not provided to theDeploymentPackager
via theDeploymentDescription
available from theTestDeployment
argument toDeploymentPackager#generateDeployment().
.The
DeployableContainer
is also capable of overriding the protocol and configuration, so that value is what needs to be first looked at, and then fallback to the defaultProtocolDefinition
if none was specified at the container level. This needsto be specified on the
TestDeployment
.Expected Behaviour
The
TestDeployment
should have the target protocol information available.Current Behaviour
This information, while available at the time the
DeploymentPackager
is called, is not provided via theTestDeployment
argument.The text was updated successfully, but these errors were encountered: