Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tls_certificate to export certificates in the chain as PEM #208

Merged

Conversation

detro
Copy link
Contributor

@detro detro commented May 11, 2022

Closes #192

Ivan De Marino and others added 2 commits May 11, 2022 12:59
…ates in the chain, in PEM format

* new computed attribute: `cert_pem` in the maps in `tls_certificate.certificates[]`
* provided testing to verify the chain contains the exact same as the source PEM, both when loading via `.content` and via `.url`
* updated documentation to reflect the new feature

Co-authored-by: Olivier Ceyral <olivier.ceyral@quicksign.com>
Co-authored-by: Philippe <phil@lighthouse.com.br>
@detro detro requested a review from a team as a code owner May 11, 2022 12:00
@detro
Copy link
Contributor Author

detro commented May 11, 2022

I need to add the CHANGELOG entry

Ivan De Marino added 2 commits May 11, 2022 14:09
… from file

This was ok except we would need to account for tests ran on windows, where the line terminations would be replaced (`\n -> \r\n`)
Copy link
Contributor

@bflad bflad left a comment

Choose a reason for hiding this comment

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

Looks good to me 🚀

@detro detro merged commit 1b40880 into main May 11, 2022
@detro detro deleted the detro/192-tls_certificate-should-export-certificates-as-pem branch May 11, 2022 17:09
jackivanov pushed a commit to jackivanov/terraform-provider-tls that referenced this pull request Aug 4, 2022
…rp#208)

* `tls_certificate` data source now exports the loaded/fetched certificates in the chain, in PEM format

* new computed attribute: `cert_pem` in the maps in `tls_certificate.certificates[]`
* provided testing to verify the chain contains the exact same as the source PEM, both when loading via `.content` and via `.url`
* updated documentation to reflect the new feature

Co-authored-by: Olivier Ceyral <olivier.ceyral@quicksign.com>
Co-authored-by: Philippe <phil@lighthouse.com.br>

* Fix documentation for the `id` attribute of `tls_certificate` data source

* Use multiline fixtures to compare PEMs produced instead of reading it from file

This was ok except we would need to account for tests ran on windows, where the line terminations would be replaced (`\n -> \r\n`)

* Updating CHANGELOG

Co-authored-by: Olivier Ceyral <olivier.ceyral@quicksign.com>
Co-authored-by: Philippe <phil@lighthouse.com.br>
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tls_certificate to export fetched certificates in PEM format
2 participants