-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
[MIG][9.0] connector_dns #6
base: 9.0
Are you sure you want to change the base?
Conversation
@elicoidal - Can you please mark this as WIP and v9 milestone? Also, how can I get write in this repo? |
Changes Unknown when pulling e2701ed on laslabs:release/9.0 into * on OCA:9.0*. |
[FIX] format [IMP] format [IMP] unit test [IMP] unit test
* Separate models by file * Add `import_synchronizer` * Add `export_synchronizer` * Add `delete_synchronizer` * Add `mapper` * Add `fail_date` to abstract bind, remove state * Add `dns.record.type` model and default data * Add external date field handling to binder * Rename `dns.domain` to `dns.zone` * Remove `line` field from `dns.record` * Change inheritance structure, add a `{model_name}.bind` framework * Add security * Code cleanup * Add test coverage * Don't cover test assets * Change bind field to `odoo_id` to ease future migration * Improve ReadMe
* Require zone in record * Fix action names in backend, zone, record * Remove states from backend and zone
* Add empty group in connector settings for DNS
* Bump version * Rename Environment to ConnectorEnvironment * Prefer odoo tags to openerp/data in views
Changes Unknown when pulling da81be8 on laslabs:release/9.0 into * on OCA:9.0*. |
@lasley the server-tool maintainers have write access. |
@elicoidal - I am a server PSC & don't have access. This looks to be in a category of its own instead. |
@lasley Indeed it was unclear at the beginning. I am in favor of adding you to the infrastructure maintainer group ( @pedrobaeza @dreispt what do you think?) |
Yeah, I agree on adding him to the PSC |
Hi everyone, does this one need additional info or could it be merged ? |
@lasley you were the lead here. Can you update us? |
I haven't made any changes here, so we should be good for review. We dropped this plan for Rancher instead, so I haven't actually tested any of this functionally as far as I remember. Would love to hear if someone has actually used it on v8 (or this version on 9), but I'm for an optimistic merge based on code review as well. |
This is a forward port of #4 for v9 (including currently pending (noahzaozao/infrastructure-dns#5). In my eyes, that PR is handled, so I need this in v9 so I can begin
connector_dns_route53
in 9Dependent on merge of: