tink allows multiple workflows to be allocated to a worker at a time. There's no technical reason why this isn't fine, but it seems to me that its probably a user mistake? Every time I've come across this I would have rather that tink let me know that a workflow was already in progress, which I would then have terminated.
If we decide not to treat it as an error should we instead give feedback
Implementation of Private Cloud using ownCloud. ownCloud is a suite of client–server software for creating and using file hosting services. This repository explains implementing ownCloud on an Ubuntu VM running on top of a Windows host for secure cloud storage
This Terraform example configurations uses the IBM Cloud provider to provision virtual machines on IBM Cloud Infrastructure (SoftLayer) and TerraForm Module ICP Deploy to prepare VSIs and deploy IBM Cloud Private on them in Highly Available configuration. This Terraform template automates best practices learned from installing ICP on IBM Cloud Infrastructure.
This Terraform configurations uses the AWS provider to provision virtual machines on AWS to prepare VMs and deploy IBM Cloud Private on them. This Terraform template automates best practices learned from installing ICP on AWS at numerous client sites in production.
These Terraform example configurations uses the SoftLayer Provider to provision servers in SoftLayer and TerraForm Module ICP Deploy to deploy IBM Cloud Private on them.
tink allows multiple workflows to be allocated to a worker at a time. There's no technical reason why this isn't fine, but it seems to me that its probably a user mistake? Every time I've come across this I would have rather that tink let me know that a workflow was already in progress, which I would then have terminated.
If we decide not to treat it as an error should we instead give feedback