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

fix: handle singular endpoints that behave as lists #787

Merged
merged 3 commits into from
Jan 28, 2025

Conversation

jacobbednarz
Copy link
Member

No description provided.

Even though not all resources expose a `id` field, we have it in the form of the `account_id` or `zone_id` parameter. We can use that instead of panic'ing.

Signed-off-by: Jacob Bednarz <[email protected]>
If the API responds with a singular result (`result = {}`) but it is a list endpoint, we need to wrap it as an array to continue with the generation steps.

Signed-off-by: Jacob Bednarz <[email protected]>
@jacobbednarz jacobbednarz merged commit 6584acd into master Jan 28, 2025
7 checks passed
@jacobbednarz jacobbednarz deleted the handle-umbrella-resources branch January 28, 2025 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant