Updated Namespace example using TF tls provider to gen CA certs #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was changed
This PR adds an example of using Hashi's tls resource to generate a CA and pass that into the Temporal Namespace resource.
The Namespace resource example was changed which triggered a change to the docs example as well.
Why?
Two approaches to change exist:
Checklist
Closes
How was this tested:
Tested locally and created a Namespace using Hashi's tls resource
Yes - see the option chose in Why