DnsimpleProvider some objects with not attribute
See original GitHub issueWhen I try to Import Data via DnsimpleProvider
the following AttributeError are given:
AttributeError: 'DnsimpleProvider' object has no attribute '_data_for_ALIAS'
AttributeError: 'DnsimpleProvider' object has no attribute '_data_for_URL'
The URL record is something specific and the ALIAS too if I understand this document correct.
In some ways it should be possible to get the data and giving an error that some settings are not dumped and not the complete dump get revoked.
This is more a feature request to make migration more easier.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Improving Validation Errors in API Clients - DNSimple Blog
Announcing several improvements related to dealing with validation errors in our API clients.
Read more >DNSimple DNS Driver Documentation - Apache Libcloud
DNSimple is a hosted DNS Service Provider that you can use to manage your domains. ... extra ( dict ) – Extra attributes...
Read more >cloudposse/s3-bucket/aws - Terraform Registry
Description: Set to false to prevent the module from creating any ... override settings in context object, except for attributes, tags, ...
Read more >terraform/CHANGELOG.md at master - GitHub
The lock_table attribute in the S3 backend configuration has been ... on some operations (#13390); provider/dnsimple: Handle 404 on DNSimple records (#13131) ...
Read more >UnboundID Identity Data Store Configuration Reference
allow-attribute-name-exceptions [ Global Configuration ] ... any-included-authz-user-group-dn [ Simple Result Criteria ]. any-included-connection-criteria ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s probably make sense to have some sort of
--ignore-unsupported
flag to do that. The way things are currently plumbed would need to change a bit to accomplish that and there’d need to be a bit of changes to the providers themselves, but it should be doable. It’d be somewhat related to the TODO task octodns/octodns#3.thank you @ross for the update on this.
I’ll close this issue now.