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

scaleway_tem_domain_validation not trigger error after timeout #2989

Closed
rtorrente opened this issue Mar 19, 2025 · 0 comments
Closed

scaleway_tem_domain_validation not trigger error after timeout #2989

rtorrente opened this issue Mar 19, 2025 · 0 comments
Assignees
Labels
bug priority:highest Bugs filled by customers, security issues tem Transactional Email issues, bugs and feature requests

Comments

@rtorrente
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

OpenTofu v1.9.0
on linux_amd64

  • provider registry.opentofu.org/hashicorp/random v3.7.1
  • provider registry.opentofu.org/scaleway/scaleway v2.51.0

Affected Resource(s)

  • scaleway_tem_domain_validation

Terraform Configuration Files

resource "scaleway_tem_domain_validation" "main" {
  domain_id = scaleway_tem_domain.main.id
  region    = "fr-par"
  timeout   = 1800
}

Expected Behavior

If validation is not complete after the timeout, an error should be triggered and resource don't have to be successfully created in tf state (As stated in the documentation)
If we run terraform apply again, we expect the scaleway_tem_domain_validation to be created again.

Actual Behavior

After the timeout, there is complete message and ressource is created in tf state.
If you run terraform apply again, it says that there is no change and validation is never triggered again.

@remyleone remyleone added the tem Transactional Email issues, bugs and feature requests label Mar 20, 2025
@remyleone remyleone added bug priority:highest Bugs filled by customers, security issues labels Mar 20, 2025
@jremy42 jremy42 closed this as completed Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug priority:highest Bugs filled by customers, security issues tem Transactional Email issues, bugs and feature requests
Projects
None yet
Development

No branches or pull requests

3 participants