Skip to content
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

[Feature] Majority of fields should be optional when updating edge rule #136

Closed
ToshY opened this issue Aug 31, 2024 · 0 comments · Fixed by #137
Closed

[Feature] Majority of fields should be optional when updating edge rule #136

ToshY opened this issue Aug 31, 2024 · 0 comments · Fixed by #137
Labels
Base API Label for Base API endpoints enhancement New feature or request

Comments

@ToshY
Copy link
Owner

ToshY commented Aug 31, 2024

When testing noticed that the addOrUpdateEdgeRule both handles add and update and has several required keys set, but the majority of those are only relevant for adding a new rule. Updating a rule only seems to require the Guid and atleast 1 Triggers (else it results in {"ErrorKey":"edgerule.invalid","Field":"EdgeRule","Message":"At least one condition is required"}).

Originally posted by @ToshY in #135 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Base API Label for Base API endpoints enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant