v1.0.0

Fix atmos terraform output JSON flag for 1.210.0+ Ben (@Benbentwo) (#81)

Summary

• Change --json to -json in OutputJsonE() so the flag is passed through to Terraform correctly
• Atmos 1.210.0+ no longer recognizes --json as an atmos-level flag; -json is the native Terraform flag
• Add compatibility note to README.yaml

Test plan

• go build ./... passes
• go vet ./... passes
• Verify atmos terraform output <component> --skip-init -s <stack> -- -json <key> works with atmos 1.210.0+

🤖 Generated with Claude Code

v0.25.0

Use atmos instead of makefile Igor Rodionov (@goruha) (#74)

what

• Use atmos instead of makefile

why

• build-harness deprecated. Use atmos instead

v0.24.0

Examples helper Ben (@Benbentwo) (#68)

what

• Examples Helper library for testing cloudposse examples

why

• trying to make this testing framework more accessible while also focusing on speed of development of tests.

v0.23.0

Added eks configs Igor Rodionov (@goruha) (#65)

what

• Move the K8S config to a separate method
• Added CleanDNSZoneID route53 zone
• Define helm metadata struct

why

• Allow the creation of dynamic clients for extensions API
• Drop orphane DNS records to teardown DNS zones
• Use metadata struct in terraform testing components that install helm charts

v0.22.0

Port EKS from cloudposse/terratest Igor Rodionov (@goruha) (#62)

what

• add eks support and k8s node assertions
• return atmos options on even if --skip-deploy-component flag is set
• remove aws-nuke package

Why

• Test EKS-related components
• Allow to read outputs when component deployment skipped
• The AWS nuke package is not used anywhere but has dependencies issues that affect tests run for all packages

Reference

• cloudposse/terratest@511d77a#diff-45f72d3df6082a81fcee9cb83cb7d0dc2fc251e42cf28b5e9709a7481ccaa6c1

v0.21.0

add configurable destination path Matt Calhoun (@mcalhoun) (#55)

what

Allow the component destination directory to be specified

why

For some more advanced components, there are nested folders

usage

This feature can be utilized by specifying --component-dest-dir or by setting suite.Config.ComponentDestDir:

func TestRunExampleSuite(t *testing.T) {
	suite := new(ExampleTestSuite)
	suite.Config.ComponentDestDir = "components/terraform/foo/bar"

	suite.AddDependency(t, "component1", "test-use2-sandbox", nil)
	suite.AddDependency(t, "component3", "test-use2-sandbox", nil)
	helper.Run(t, suite)
}

v0.20.0

Fix outputs when workspace switched Igor Rodionov (@goruha) (#59)

what

• Skip output string "Switch workspace"
• Added AWS Waf helper functions

Why

• Solve problems with outputs when reusing component for multiple configrations
• Required to test WAF component

v0.19.0

fix dependencies only flag bug Matt Calhoun (@mcalhoun) (#58)

what

Fix a bug where using the --only-deploy-dependencies flag was still running tests

v0.18.0

Fix route53 zone Igor Rodionov (@goruha) (#56)

what

• Remove if case in GetDNSZoneByNameE method

why

• The if cases is useless

v0.17.0

Extend aws package Igor Rodionov (@goruha) (#54)

what

• Added GetDNSZoneByNameE

why

• Required for dns-delegated component tests