-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[scd] dangling implicit subscription when OIR with implicit subscription is mutated #1056
Comments
@BenjaminPelletier FYI I'll start working on this (but can't assign myself) |
This was referenced Jul 18, 2024
Open
13 tasks
This was referenced Sep 6, 2024
Shastick
added a commit
to Orbitalize/dss
that referenced
this issue
Sep 9, 2024
This is a rework of interuss#1057 after most changes for interuss#1088 have landed. The DSS built from this PR successfully passed the new qualifier's implicit subscription handling scenario, although that scenario still needs to be extended to cover all corner cases. The PR is open for review, as it addresses interuss#1056
mickmis
pushed a commit
that referenced
this issue
Sep 9, 2024
This is a rework of #1057 after most changes for #1088 have landed. The DSS built from this PR successfully passed the new qualifier's implicit subscription handling scenario, although that scenario still needs to be extended to cover all corner cases. The PR is open for review, as it addresses #1056
This has been addressed by #1109 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When updating an Operational Intent Reference (OIR) for which an implicit subscription was created, if the subscription id is not specified and the parameters for creating an implicit subscription are specified, the DSS will create a new implicit subscription without deleting the previous one.
This is the region of the code where it happens.
To Reproduce
Expected behavior
After the mutation of an OIR with an implicit subscription, under all circumstances, either the existing implicit subscription has been reused and properly updated, or a new implicit subscription has been created, and the previous one removed if it is no longer attached to any OIR.
Additional questions/discussion
Options to solve this:
A) On mutation, when no subscription ID is specified and the parameters for an implicit subscription are specified, it is acceptable to reuse the existing implicit subscription and mutate it if necessary.
B) On mutation, when no subscription ID is specified and the parameters for an implicit subscription are specified, delete the previous implicit subscription, if it exists and has no more OIRs attached, and create a new one.
I'm in favor of option B here, as I'm not sure that allowing to indirectly mutate the callback URL of an implicit subscription is a desirable feature:
Side question: On mutation, when no subscription and no implicit subscription parameters are specified, should we:
Another way to look at this question is to ask how do we remove an implicit subscription from an OIR in the ACCEPTED state without deleting the OIR and re-creating it?
The text was updated successfully, but these errors were encountered: