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

Investigate schema relations bug in Distribution in aws_cloudfront #2285

Open
depombo opened this issue Mar 20, 2023 · 1 comment
Open

Investigate schema relations bug in Distribution in aws_cloudfront #2285

depombo opened this issue Mar 20, 2023 · 1 comment
Assignees
Labels
bug Something isn't working cloud coverage increase cloud coverage for IaSQL

Comments

@depombo
Copy link
Member

depombo commented Mar 20, 2023

We are getting stopgap lazy loader issues here. It could be as simple as having an optional AWS field as not nullable, but could be something else

https://discord.com/channels/920684574231646229/1086405212958380103

@depombo depombo converted this from a draft issue Mar 20, 2023
@depombo depombo added bug Something isn't working cloud coverage increase cloud coverage for IaSQL labels Mar 20, 2023
@depombo depombo moved this from In Progress to Todo in IaSQL Sprint Board Mar 20, 2023
@aguillenv aguillenv moved this from Todo to In Progress in IaSQL Sprint Board Mar 22, 2023
@aguillenv
Copy link
Contributor

aguillenv commented Mar 24, 2023

So I've been trying to reproduce and I've seen some issues but I have not been able to reproduce the main error that was during the sync apparently. Some of the small task and/or issues seen on my branch cf-dist:

  • Try to replicate a failure syncing the distributions
  • callerReference is set to nullable but it is not
  • if you tried to create a distribution with an empty json for the mandatory fields it fails on creation. I think that should be handled properly in the mapper. or maybe a trigger? I need to understand better cf distributions.
  • There's an issue with the revert logic :/ specifically for type json fields. The query generated is not setting the type properly. I think I've solved this for the get_sql_* RPCs but they do not use the same code. Maybe I should find a way to make them share as much as possible for this logic...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cloud coverage increase cloud coverage for IaSQL
Projects
None yet
Development

No branches or pull requests

2 participants