You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment there doesn't seem to be any support for configuring preview environments to be different from production. In the case of my project the things I'm missing in the terraform provider are:
Setting a preview_plan in the render_web_service provider
Setting a preview_plan in the render_postgres provider
Setting preview_value (for each env var) in the render_env_group provider (and also for env vars within web service and cron job)
The render.com documentation describes all of these. I'd really like to migrate away from render.yml to terraform but I can't without access to these settings, is there any plan to add them in the near future?
The text was updated successfully, but these errors were encountered:
Render preview environments require using Blueprints at this time. We plan to add support for managing preview environments via other methods in the future.
You may be able to use a combination of Terraform and Github Actions to create a similar preview environment experience. You can run terraform apply on each PR and push, and set the preview plans and values in the TF config based on whether the branch you are working from == main.
At the moment there doesn't seem to be any support for configuring preview environments to be different from production. In the case of my project the things I'm missing in the terraform provider are:
preview_plan
in therender_web_service
providerpreview_plan
in therender_postgres
providerpreview_value
(for each env var) in therender_env_group
provider (and also for env vars within web service and cron job)The render.com documentation describes all of these. I'd really like to migrate away from render.yml to terraform but I can't without access to these settings, is there any plan to add them in the near future?
The text was updated successfully, but these errors were encountered: