Skip to content
This repository was archived by the owner on May 15, 2025. It is now read-only.

Comments

galasactl should not set submission id - it should come from the server or remain blank#349

Merged
techcobweb merged 1 commit intomainfrom
mcobbett-dont-set-submission-id-in-client
Mar 12, 2025
Merged

galasactl should not set submission id - it should come from the server or remain blank#349
techcobweb merged 1 commit intomainfrom
mcobbett-dont-set-submission-id-in-client

Conversation

@techcobweb
Copy link
Contributor

@techcobweb techcobweb commented Mar 12, 2025

Signed-off-by: Mike Cobbett 77053+techcobweb@users.noreply.github.com

Why ?

Galasa client should not set the submission id itself, but should only get one from a server-side response.

…er or remain blank

Signed-off-by: Mike Cobbett <77053+techcobweb@users.noreply.github.com>
@techcobweb techcobweb merged commit 2863109 into main Mar 12, 2025
3 checks passed
@techcobweb techcobweb deleted the mcobbett-dont-set-submission-id-in-client branch March 12, 2025 13:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants