It is currently possible to provide a --limit when calling the 'boardwalk' command, to further restrict and sub-select the host pattern present within a Workspace's configuration. However, prior to this commit, the contents, if any, of the limit were not displayed on the boardwalkd web UI.
Thus, the worker_limit is added to the WorkspaceDetails model, thus allowing for the --limit (if any) to be sent to boardwalkd upon workflow execution.
As we use the limit as directly defined from the worker--and as it is possible to not define a limit, we display 'unknown' on the UI if the limit is not defined. That could be caused by the aforementioned undefined limit--thus being equivalent to an all limit--or because the boardwalk client was not updated, and thus does not send the limit data in the WorkspaceDetails sent to the server upon initiation of a workflow.
Compatible with prior version, however if a --limit is provided in an older CLI worker, it will not be reflected on the web UI.
Resolves Issue #56.
How was this tested?
Tested using the ShouldSucceedTestWorkspace, against the version this PR creates, as well as the prior version which doesn't send the limit. Both succeed.
Checklist
[x] Have you updated the version in the [tool.poetry] section of
the pyproject.toml file (if applicable)?
What and why?
It is currently possible to provide a
--limitwhen calling the 'boardwalk' command, to further restrict and sub-select the host pattern present within a Workspace's configuration. However, prior to this commit, the contents, if any, of the limit were not displayed on the boardwalkd web UI.Thus, the
worker_limitis added to the WorkspaceDetails model, thus allowing for the--limit(if any) to be sent to boardwalkd upon workflow execution.As we use the limit as directly defined from the worker--and as it is possible to not define a limit, we display 'unknown' on the UI if the limit is not defined. That could be caused by the aforementioned undefined limit--thus being equivalent to an
alllimit--or because the boardwalk client was not updated, and thus does not send the limit data in the WorkspaceDetails sent to the server upon initiation of a workflow.Compatible with prior version, however if a
--limitis provided in an older CLI worker, it will not be reflected on the web UI.Resolves Issue #56.
How was this tested?
Tested using the ShouldSucceedTestWorkspace, against the version this PR creates, as well as the prior version which doesn't send the limit. Both succeed.
Checklist
versionin the[tool.poetry]section of thepyproject.tomlfile (if applicable)?