
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>
1.2 KiB
1.2 KiB
page_title, subcategory, description
page_title | subcategory | description |
---|---|---|
gitea_public_key Resource - terraform-provider-gitea | gitea_public_key manages ssh key that are associated with users. |
gitea_public_key (Resource)
gitea_public_key
manages ssh key that are associated with users.
Example Usage
resource "gitea_user" "test" {
username = "test"
login_name = "test"
password = "Geheim1!"
email = "test@user.dev"
must_change_password = false
}
resource "gitea_public_key" "test_user_key" {
title = "test"
key = file("${path.module}/id_ed25519.pub")
username = gitea_user.test.username
}
Schema
Required
key
(String, Sensitive) An armored SSH key to addtitle
(String) Title of the key to addusername
(String) User to associate with the added key
Optional
read_only
(Boolean) Describe if the key has only read access or read/write
Read-Only
created
(String)fingerprint
(String)id
(String) The ID of this resource.type
(String)