Skip to content

Conversation

@lasley
Copy link

@lasley lasley commented Oct 11, 2016

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 9

Dependent on merge of:

@lasley
Copy link
Author

lasley commented Oct 11, 2016

@elicoidal - Can you please mark this as WIP and v9 milestone? Also, how can I get write in this repo?

@coveralls
Copy link

coveralls commented Oct 11, 2016

Coverage Status

Changes Unknown when pulling e2701ed on laslabs:release/9.0 into * on OCA:9.0*.

lasley and others added 8 commits October 11, 2016 08:24
[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
@coveralls
Copy link

coveralls commented Oct 11, 2016

Coverage Status

Changes Unknown when pulling da81be8 on laslabs:release/9.0 into * on OCA:9.0*.

@elicoidal elicoidal added this to the 9.0 milestone Oct 13, 2016
@elicoidal
Copy link

elicoidal commented Oct 13, 2016

@lasley the server-tool maintainers have write access.
We are discussing on smaller maintainer groups for the future but not yet finally designed.
do not hesitate to ping me or @pedrobaeza in the meantime

@lasley
Copy link
Author

lasley commented Oct 13, 2016

@elicoidal
Copy link

@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?)

@pedrobaeza
Copy link
Member

Yeah, I agree on adding him to the PSC

@lasley lasley mentioned this pull request Oct 14, 2016
12 tasks
@flotho
Copy link
Member

flotho commented Dec 10, 2017

Hi everyone, does this one need additional info or could it be merged ?

@elicoidal
Copy link

@lasley you were the lead here. Can you update us?

@lasley
Copy link
Author

lasley commented Dec 11, 2017

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.

@github-actions
Copy link

github-actions bot commented Jun 8, 2025

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

migration needs review stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants