You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command atmos terraform shell launches a shell in the component base directory, not the directory of the selected component, but terraform commands only work when the current directory is the directory of the component.
Expected Behavior
atmos terraform shell <component> should launch a shell in the directory of the component, specifically .component_info.terraform_config.path as determined by atmos describe component <component>.
Steps to Reproduce
Run atmos terraform shell <component> -s <stack> for any valid stack and component, and note that your current working directory is Atmos-configured components.terraform.base_path and not the component's Terraform directory
Screenshots
No response
Environment
Atmos v1.63.0
Geodesic 2.9.1-debian
Additional Context
The premise of atmos terraform shell is that it prepares you to use unadorned Terraform commands at the command line that operate on the designated component with the designated stack configuration. Without being in the proper working directory, terraform does not work and the premise is not fulfilled.
The text was updated successfully, but these errors were encountered:
@Nuru this is not the behavior I experience, I DO get dropped into the component's directory, not my parent directory of all components.
config:
# See full configuration options @ https://github.com/cloudposse/atmos/blob/master/examples/complete/atmos.yamlbase_path: ""components:
terraform:
base_path: "components"auto_generate_backend_file: truestacks:
base_path: "stacks"included_paths:
- "org/**/*"name_pattern: "{stage}"excluded_paths:
- "**/_*.yaml"# Do not consider any file beginning with "_" as a stack filelogs:
verbose: truecolors: truecommands:
- name: updescription: Run terraform `init -upgrade` for a given component instancearguments:
- name: componentdescription: Name of the componentflags:
- name: stackshorthand: sdescription: Name of the stackrequired: truesteps:
- atmos terraform init {{ .Arguments.component }} -s {{ .Flags.stack }} -upgrade
Describe the Bug
The command
atmos terraform shell
launches a shell in the component base directory, not the directory of the selected component, butterraform
commands only work when the current directory is the directory of the component.Expected Behavior
atmos terraform shell <component>
should launch a shell in the directory of the component, specifically.component_info.terraform_config.path
as determined byatmos describe component <component>
.Steps to Reproduce
Run
atmos terraform shell <component> -s <stack>
for any valid stack and component, and note that your current working directory is Atmos-configuredcomponents.terraform.base_path
and not the component's Terraform directoryScreenshots
No response
Environment
Additional Context
The premise of
atmos terraform shell
is that it prepares you to use unadorned Terraform commands at the command line that operate on the designated component with the designated stack configuration. Without being in the proper working directory,terraform
does not work and the premise is not fulfilled.The text was updated successfully, but these errors were encountered: