force forward auth redeployment when tls secret changes #2771
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viniciusdc
reviewed
Aug 5, 2025
Comment on lines
+174
to
179
| data "kubernetes_secret_v1" "cert_secret" { | ||
| metadata { | ||
| name = var.cert_secret_name | ||
| namespace = var.namespace | ||
| } | ||
| } |
Contributor
There was a problem hiding this comment.
What happens if there is no secret available, will this block the deployment? considering backwards compatibility... maybe use a count
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference Issues or PRs
I believe this will fix #2772, but I haven't tested it yet.
What does this implement/fix?
Put a
xin the boxes that applyTesting
How to test this PR?
Any other comments?