-
Notifications
You must be signed in to change notification settings - Fork 630
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
Adding support for fallback domains #1356
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing documentation, tests failing, improper cloudflare-go fields usage.
Added documentation. Tests should all pass once cloudflare-go is bumped (depends on cloudflare/cloudflare-go#761). |
Marking this pull request as stale due to 14 days of inactivity. This helps our maintainers find and focus on the active pull requests. If this pull request receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
@patryk I believe this is waiting on a cloudflare-go release and to bump the version here. Is there a plan to do that? |
Update: resourceCloudflareFallbackDomainUpdate, | ||
Delete: resourceCloudflareFallbackDomainDelete, | ||
Importer: &schema.ResourceImporter{ | ||
State: schema.ImportStatePassthrough, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! this actually found a bug 🤗 we have defined resourceCloudflareFallbackDomainImport
but not used it.
No description provided.