Skip to content

Conversation

@mayasrl
Copy link

@mayasrl mayasrl commented Oct 22, 2025

What I added

Migration guide - If you're already using Tsuru and want to start managing it with Terraform, this walks you through it. Covers how to import your existing stuff without breaking anything.

Tutorials

  • Getting started - Install the provider, create an app
  • Managing apps - Environment variables, domains, autoscaling
  • Jobs - Scheduled tasks and one-off jobs
  • Infrastructure - Clusters, pools, plans

Real examples

  • Complete web app setup
  • Scheduled job
  • Cluster configuration

Rewrote some resource docs - The app and cluster docs now have actual examples instead of just the schema. Added troubleshooting tips too.

Why

Right now the docs are mostly auto-generated schemas. Hard to figure out how things actually work. These changes should make it way easier to get started and understand how to use the provider.

Let me know if you want me to change anything!

@crgisch
Copy link
Member

crgisch commented Oct 24, 2025

First of all, thank you for your contribution during Hacktoberfest! We appreciate it!
Right now the team is overwhelmed by external and internal PRs, so we might take a while to get to this one!
Thank you for understanding!

Meanwhile, some of this MR a is duplicated of another one: #74, in case you also want to take a look at it and give your opinion


## Contributing

Found an issue or want to add more examples? Contributions welcome.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: replace Contributions welcome. for Contributions are welcome!

@@ -1,12 +1,55 @@
# Terraform Provider Tsuru [![GitHub tag (latest SemVer)](https://img.shields.io/github/v/tag/tsuru/terraform-provider-tsuru?label=release)](https://github.com/tsuru/terraform-provider-tsuru/releases) [![license](https://img.shields.io/github/license/tsuru/terraform-provider-tsuru.svg)]()
# Terraform Provider Tsuru - Improved Documentation

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if the text - Improved Documentation is necessary. If we merge this will be the only documentation.

- Usage
- [Provider Documentation](https://registry.terraform.io/providers/tsuru/tsuru/latest/docs)
- [Tsuru Documentation](https://docs.tsuru.io/)
Better docs for the terraform-provider-tsuru with practical examples, migration guides, detailed resource documentation, and step-by-step tutorials.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be Documentation for the .... in place of Better docs ...

"CACHE_URL" = "redis://host:port"
}

no_restart = false
Copy link

@pauloricardokoch pauloricardokoch Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looking the terraform resource, I think the tag should be called restart_on_update
https://registry.terraform.io/providers/tsuru/tsuru/latest/docs/resources/app_env

target = "80%"
}

schedules = [

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field schedules seems to be not functional, check the docs for clarification
https://registry.terraform.io/providers/tsuru/tsuru/latest/docs/resources/app_autoscale

command = ["echo", "Hello from Tsuru Job!"]
}

schedule = "@every 1h"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not familiar with this tag. Maybe we should have 0 */1 * * *

}
}
pools = ["pool1", "pool2"]
Copy link

@pauloricardokoch pauloricardokoch Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Successfully merging this pull request may close these issues.

3 participants