Skip to content

Conversation

RoseSecurity
Copy link
Contributor

@RoseSecurity RoseSecurity commented Oct 7, 2025

what

  • Added a new Go test suite in test/component_test.go that uses Cloud Posse's test-helpers to deploy and test Atmos Terraform components, including tests for Datadog monitor components and enabled/disabled flags.
  • Introduced a go.mod file specifying dependencies for the test suite, including test-helpers, testify, and other indirect dependencies required for infrastructure testing.
  • Added detailed Atmos configuration in test/fixtures/atmos.yaml to define base paths, component and stack settings, logging, and template support for tests.
  • Created stack and component fixture files for various test scenarios, such as account maps, Datadog configuration, and Datadog monitor use cases (both enabled and disabled), under test/fixtures/stacks/catalog and test/fixtures/stacks/orgs/default/test.
  • Added a vendor manifest (test/fixtures/vendor.yaml) to specify the sources and versions of vendored Terraform components used in the tests.
  • Updated .gitignore to exclude test state, cache, and other generated files from version control.
  • Removed placeholder files and scripts that are no longer needed, such as the old test/README.md and test/run.sh.

These changes collectively establish a robust and reproducible testing framework for Terraform components using Atmos and Cloud Posse conventions.

why

  • This pull request introduces a test suite for the component, adding Go-based component tests, test fixtures, and supporting configuration files. The main focus is to enable automated testing of Terraform components, particularly those related to Datadog monitors

references

Introduce a new Go-based integration test suite for the Datadog monitor
component using cloudposse/test-helpers. Add all necessary fixtures,
stack configs, and vendored dependencies to support local and CI
testing. Remove placeholder files and scripts no longer needed.
Copy link

coderabbitai bot commented Oct 7, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

mergify bot commented Oct 7, 2025

Important

Do not edit the README.md directly. It's auto-generated from the README.yaml

Please update the README.yaml file instead.

Could you fix it @RoseSecurity? 🙏

@mergify mergify bot added the triage Needs triage label Oct 7, 2025
- Add handling for Datadog App key in test suite, storing it in SSM
  alongside the API key to avoid conflicts in parallel tests.
- Refactor struct field names for consistency and clarity.
- Update SSM parameter paths and cleanup logic for both API and App keys.
- Fix stack fixture metadata and monitor config path globbing for
  improved test reliability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Needs triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant