Commit Graph

9 Commits

Author SHA1 Message Date
557ea2673a New resources for managing team membership (#36)
This PR adds two new resources, _gitea_team_membership_ & _gitea_team_members_, in an attempt to decouple _gitea_team_ resources from team memberships. This facilitates the removal of members from teams without altering/recreating an existing _team_ resource.

This PR adresses this issue: https://gitea.com/gitea/terraform-provider-gitea/issues/30

The ability to set members in the _gitea_team_ resource has been removed.

The resources proposed here are inspired by similar resources in the _GitHub_ provider:
* [team_members](https://registry.terraform.io/providers/integrations/github/latest/docs/resources/team_members)
* [team_membership](https://registry.terraform.io/providers/integrations/github/latest/docs/resources/team_membership)

# gitea_team_members
A single resource manages all members of a team.

- This resource must be recreated when membership changes. This means, that other team members will temporarily loose their membership until the recreation of the resource is complete.
- If the recreation of the resource fails, other users will have lost their membership until the resource can be recreated.

# gitea_team_membership
A single resource holds the relationship between a single user and a single team.

-  Memberships can be deleted without affecting other users.

Reviewed-on: https://gitea.com/gitea/terraform-provider-gitea/pulls/36
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Co-authored-by: Tobias Balle-Petersen <tobiasbp@gmail.com>
Co-committed-by: Tobias Balle-Petersen <tobiasbp@gmail.com>
2023-11-16 00:52:16 +00:00
683696a756 Add repository webhook resource (#28)
Co-authored-by: techknowlogick <techknowlogick@noreply.gitea.com>
Reviewed-on: https://gitea.com/gitea/terraform-provider-gitea/pulls/28
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Co-authored-by: Petar Nikolovski <petar.nikolovski@protonmail.com>
Co-committed-by: Petar Nikolovski <petar.nikolovski@protonmail.com>
2023-10-24 19:46:11 +00:00
cc8760c9fd lerentis's changes (#12)
Changes from lerentis's fork.

Co-authored-by: Tobias Trabelsi <lerentis@uploadfilter24.eu>
Reviewed-on: https://gitea.com/gitea/terraform-provider-gitea/pulls/12
2023-09-06 01:44:01 +00:00
acf6b121c9 Fetch correct value for name variable in gitea_repo data source (#9)
Hi all,

I've noticed that data source for `gitea_repo` is not working. Instead of trying to fetch data from `/api/v1/repos/<username>/<name>` it sends a reques as `/api/v1/repos/<username>/<username>`. I've updated the code to fix this.

Signed-off-by: petar.nikolovski <petar.nikolovski@united.cloud>

Reviewed-on: https://gitea.com/gitea/terraform-provider-gitea/pulls/9
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Co-authored-by: petar.nikolovski <petar.nikolovski@noreply.gitea.com>
Co-committed-by: petar.nikolovski <petar.nikolovski@noreply.gitea.com>
2023-09-05 14:31:48 +00:00
7ba385d44a propose features upstream (#2)
Hi @techknowlogick 👋

as discussed on twitter the changes i made on my fork 😃

not sure if you are aware of this but currently hashicorp only allows publishing via github, so if you want to publish this provider to the terraform registry as well, feel free to also take a look at my goreleaser config and drone/github actions usage her: https://git.uploadfilter24.eu/lerentis/terraform-provider-gitea

Co-authored-by: Tobias Trabelsi <lerentis@uploadfilter24.eu>
Reviewed-on: https://gitea.com/gitea/terraform-provider-gitea/pulls/2
Co-authored-by: lerentis <lerentis@noreply.gitea.io>
Co-committed-by: lerentis <lerentis@noreply.gitea.io>
2022-08-22 23:54:13 +08:00
6879c07e9f get repo as datasource 2022-04-01 00:23:50 -04:00
35c4b897fb correct typo 2022-03-31 20:15:25 -04:00
75efa3bc7c update to latest sdk 2022-03-31 19:19:14 -04:00
4fbedb01b5 Initial commit 2022-03-31 17:24:00 -04:00