cloudposse / cloudposse/atmos

Allow setting global `terraform_workspace_pattern`

Open
#2,066 0 comments 2 reactions 2 assignees Claimed by @osterman View on GitHub
Dominant language
Go
Stars
1.4k
Forks
175
Avg merge
2d 3h
Merged PRs (30d)
134

Description

### Describe the Feature

It is not currently possible to set `terraform_workspace_pattern` globally. This results in all of my components having a block similar to:

```
components:
terraform:
network:
metadata:
terraform_workspace_pattern: "{component}"
...
```

### Expected Behavior

setting `terraform_workspace_pattern` in a global context should considered when evaluating terraform workspace name.

### Use Case

The default of `{stage}-{component}` is redundant/unneeded for my situation as I keep each stage's state files in a separate respective AWS account / bucket so there is no chance of conflicts.

### Describe Ideal Solution

It would be useful to allow setting `terraform_workspace_pattern` in `atmos.yaml` to DRY up component declarations.

### Alternatives Considered

_No response_

### Additional Context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.