4 Commits (6a08e893e37ee2ca1dde05d36bbee5d8edca790d)

Author	SHA1	Message	Date
Martin Atkins	f09a5661cf	tls_self_signed_cert reference subject doc from tls_cert_request ... tls_self_signed_cert is really just a shorthand over tls_cert_request and tls_locally_signed_cert, so rather than duplicating all of this documentation and risking that it will get out of sync (since the structure is shared in the implementation) we'll just link to the existing docs. This fixes #5343.	10 years ago
Martin Atkins	25bd43d6f4	Export public keys from tls_private_key ... In most cases private keys are used to produce certs and cert requests, but there are some less-common cases where the PEM-formatted keypair is used alone. The public_key_pem attribute supports such cases. This also includes a public_key_openssh attribute, which allows this resource to be used to generate temporary OpenSSH credentials, so that e.g. a Terraform configuration could generate its own keypair to use with the aws_key_pair resource. This has the same caveats as all cases where we generate private keys in Terraform, but could be useful for temporary/throwaway environments where the state either doesn't live for long or is stored securely. This builds on work started by Simarpreet Singh in #4441 .	10 years ago
Silas Sewell	309e697a52	provider/tls: add locally signed certificates ... This allows you to generate and sign certificates using a local CA.	11 years ago
Martin Atkins	f6fd41e7b5	tls provider ... As of this commit this provider has only logical resources that allow the creation of private keys, self-signed certs and certificate requests. These can be useful when creating other resources that use TLS certificates, such as AWS Elastic Load Balancers. Later it could grow to include support for real certificate provision from CAs using the LetsEncrypt ACME protocol, once it is stable.	11 years ago