Fix for fluent integration tests for Windows #438
Merged
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.
Description of the issue
The fluent tests for Windows reference out-of-scope resources in the
provider.tf
and don't wait for theamazon-cloudwatch
namespace before creating thekubernetes_config_map.cwagentconfig
andkubernetes_service_account.fluentbit_service
resources.Description of changes
provider.tf
.kubernetes_config_map.cwagentconfig
andkubernetes_service_account.fluentbit_service
resources depend onkubernetes_namespace.namespace
.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Ran locally with
terraform apply
:Made following changes for it to work locally since the linux binary doesn't work on Mac:
Ran workflow: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/12147698823