Update `overrides` section. Add tests @aknysh (#1259)
what
- Update
overrides
section - Add tests
why
- Improve the overrides section to detect and process the inline overrides in the imported stack manifests to allow the configurations like these:
vars:
stage: prod
import:
# The `overrides` is imported after the component `c1` is imported.
# The `overrides` should not override anything for the component `c1`.
- catalog/c1
- catalog/overrides
vars:
stage: prod
import:
# The `overrides` is imported before the component `c1` is imported.
# The `overrides` will override the component `c1` configuration.
- catalog/overrides
- catalog/c1
Configure YAML formatting in atmos describe commands @Cerebrovinny (#1180)
what
- Make the indentation and empty components configurable trough atmos.yaml file
why
Include Empty False (default config)
# Atmos Describe Settings
describe:
settings:
include_empty: false
# Global settings
settings:
terminal:
tab_width: 4 # default should be 2
Add pager for `atmos describe component` @samtholiya (#1215)
what
- Add pager for
atmos describe component
why
- Better UX
Custom columns docs @Cerebrovinny (#1219)
what
- Add
atmos list
custom columns documentation
why
- We have multiple places using custom columns in atmos list but are missing documentation
Implement `atmos list vendor` @Cerebrovinny (#1192)
what
- Implement
atmos list vendor
command to list all vendor configurations in multiple formats (table, json, yaml, csv, tsv). - Implements filtering and custom columns.
why
- Provides a way to view and audit all vendor configurations.
Nested components for `atmos list vars` @Cerebrovinny (#1225)
what
- Enabled
atmos list vars
and atmos list values to correctly display information for nested components (e.g.,apis/weather
,eks/cluste
r).
why
- previously we assume and extract only the basename of nested components
- These changes ensure the full component path is used for both existence checks and data querying.