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

[Resource Addon][Feature] Add Maintenance Windows and Periodic Backups Config #170

Open
josephpage opened this issue Jul 7, 2023 · 2 comments

Comments

@josephpage
Copy link
Contributor

josephpage commented Jul 7, 2023

Now that it's implemented in go-scalingo, we can add maintenance windows and periodic backups configuration here! (Scalingo/go-scalingo#339)

Preview :

resource "scalingo_addon" "redis" {
  provider_id        = "scalingo-redis"
  plan               = "redis-sandbox"
  app                = scalingo_app.test_app.id
  database_features  = ["force-ssl", "redis-aof"]
  
  # run the maintenance only on Sundays at approximately 2am
  maintenance_window = {
    weekday_utc       = 7
    starting_hour_utc = 2 
  }
  
  # backup database every day at 1am, disabled if empty or null
  periodic_backups_scheduled_at = [1]
}

Sounds great! I can't wait!

@josephpage josephpage changed the title [Database][Feature] Add maintenance windows [Resource Addon][Feature] Add maintenance windows Jul 7, 2023
@Soulou
Copy link
Member

Soulou commented Jul 19, 2023

@josephpage Feature is not yet globally available, it will be added to the provider once done :-D (You're so reactive)

@josephpage josephpage changed the title [Resource Addon][Feature] Add maintenance windows [Resource Addon][Feature] Add Maintenance Windows and Periodic Backups Config Aug 12, 2024
@josephpage
Copy link
Contributor Author

Hello @Soulou,
I've just added the "Periodic Backups Config" to the Issue, which I'd also like to see implemented on the provider.
I hope it happens !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants