Releases: cloudposse/atmos
Releases · cloudposse/atmos
v1.142.0
Introduce a centralized theming system for consistent UI styling @Cerebrovinny (#913)
what
- Introduced a centralized theming system for consistent UI styling
- Moved terminal colors to global constants
- Added theme-based color and style configurations
why
- Centralize color and style management across the application
- Make it DRY and consistent
Contributors
Cerebrovinny
Assets 17
v1.141.0
Update the descriptions of Atmos commands @samtholiya (#845)
what
- Update the descriptions of Atmos commands
why
- Improve clarity and specificity regarding Atmos commands functionality
Contributors
samtholiya
Assets 17
v1.140.0
Add `--query` (shorthand `-q`) flag to all `atmos describe ` commands @aknysh (#920)
what
- Added
--query(shorthand-q) flag to allatmos describe <subcommand>commands - Updated CLI command documentation to reflect new querying functionality
- Added examples for new query-based commands
why
- Query (and filter) the results of
atmos describe <subcommand>commands using yq expressions - Before, an external
yqorjqbinary was required to query/filter the results ofatmos describecommands. With theyqfunctionality now embedded in Atmos, installing theyqbinary is not required
examples
atmos describe component vpc -s plat-ue2-prod --query .vars
atmos describe component vpc -s plat-ue2-prod -q .vars.tags
atmos describe component vpc -s plat-ue2-prod -q .settings
atmos describe component vpc -s plat-ue2-prod --query .metadata.inherits
atmos describe stacks -q keys # this produces the same result as the native `atmos list stacks` command
atmos describe config -q .stacks.base_path
atmos describe workflows -q '.0 | keys'
atmos describe affected -q <yq-expression>
atmos describe dependents -q <yq-expression>
references
Contributors
aknysh
Assets 17
v1.139.0
`TF_CLI_ARGS_*` Handling @milldr (#898)
what
- Added logic and warning messages when the user specifies any
TF_CLI_*environment variable, since this may conflict with Atmos behavior. - Append any TF_CLI env vars to the determined TF_CLI env var for
terraform shell
why
- When executing Terraform Shell, we should append generate var file to the (if) specified env var rather than overwriting it
- When executing Terraform, var files are already appended (merged). We should add a warning nonetheless
atmos terraform shell
atmos terraform plan
Contributors
milldr
Assets 17
v1.138.0
Implement `atmos about` and `atmos support` commands @Cerebrovinny (#909)
what
- Implement
atmos aboutandatmos supportcommands
why
- Help users to find information about Atmos and Cloud Posse support
Support
About
Contributors
Cerebrovinny
Assets 17
v1.137.0
Merge Atmos specific and terraform/helmfile help documentation @samtholiya (#857)
what
- Merge Atmos specific and terraform/helmfile help documentation
why
- Show the native terraform/helmfile commands and Atmos-specific terraform/helmfile commands
Contributors
samtholiya and milldr
Assets 17
v1.136.0
🚀 Enhancements
Support for a circuit breaker to avoid recursive calls to Atmos custom commands (infinite loop) @Listener430 (#906)
what
- Support for a circuit breaker to avoid recursive calls to Atmos custom commands
why
- Avoid infinite loops
test
Add-on to atmos.yaml
The circuit breaker in use
Contributors
Listener430
Assets 17
v1.135.0
Implement Custom Markdown Styling for Workflow Commands @Cerebrovinny (#853)
Implement Custom Markdown Styling for Workflow Commands
What
- Added custom markdown styling support for workflow command outputs
- Implemented a configurable markdown styling system through
atmos.yaml - Added fallback to built-in default styles when no custom styles are defined
- Added new workflow error templates in markdown format
- Improved code readability and maintainability in markdown rendering logic
Why
- Enhances user experience
- Allows users to define their own color schemes and styling preferences
- Improves error message readability with consistent formatting and styling
- Makes the CLI more accessible by supporting both default and custom color schemes
- Follows modern CLI design patterns with rich text formatting
Technical Details
- Added
markdownsettings section inatmos.yamlfor custom styling configuration - Implemented style inheritance system (custom styles override built-in defaults)
- Added support for styling:
- Document text and background colors
- Headings (H1-H6) with custom colors and formatting
- Code blocks with syntax highlighting
- Links with custom colors and underlining
- Blockquotes and emphasis styles
- Enhanced error handling with structured markdown templates
- Added proper fallback mechanisms for style configuration
References
- Implements styling using glamour for terminal markdown rendering
- Follows ANSI terminal styling standards
- https://github.com/charmbracelet/bubbletea
- https://github.com/charmbracelet
- https://github.com/charmbracelet/glow
- https://github.com/charmbracelet/glamour/blob/master/styles/gallery/README.md
Testing
The implementation has been tested with:
- Custom styling configurations in
atmos.yaml
- Default styling fallback when no custom styles are defined
Contributors
Cerebrovinny
Assets 17
v1.134.0
🚀 Enhancements
Support default values for arguments in Atmos custom commands @Listener430 (#905)
what
- Support default values for arguments in Atmos custom commands in
atmos.yaml
why
- Allow specifying default values and don't not require the users to provide the values when invoking the custom commands
before
a custom cli-command is defined
after
Contributors
Listener430
Assets 17
v1.133.0
Replace `path` with `filepath` @haitham911 @aknysh (#900)
what
Replace path with filepath
why
- Different operating systems use different path separators (
/on Unix-based systems like Linux and macOS, and\on Windows).
filepathpackage automatically handles these differences, making code platform-independent. It abstracts the underlying file system separator, so we don't have to worry about whether you're running on Windows or Unix-based systems
Contributors
aknysh and haitham911