Describe the Feature
Add integrations to the output of the atmos describe affected
Expected Behavior
When I run :
atmos describe affected --ref refs/heads/main --verbose=true
the output is:
{
"stack": "pepe-ue2-lab",
"component_type": "terraform",
"component": "vpc",
"affected": "stack.vars"
}
]
if atlantis integration is enabled it will be useful to have the project name added to the output like 👍🏽
{
"stack": "pepe-ue2-lab",
"component_type": "terraform",
"component": "vpc",
"affected": "stack.vars"
"atlantis_project_name": "pepe-ue2-lab-vpc"
}
]
Use Case
since Atlantis supports dynamically generated atlantis.yaml files it is possible to generate an atlantis.yaml for only the affected component/s and this way limit the blast radius of a PR significantly.
Alternatives Considered
parsing yaml until is not fun anymore....
Describe the Feature
Add integrations to the output of the
atmos describe affectedExpected Behavior
When I run :
atmos describe affected --ref refs/heads/main --verbose=truethe output is:
if atlantis integration is enabled it will be useful to have the project name added to the output like 👍🏽
Use Case
since Atlantis supports dynamically generated
atlantis.yamlfiles it is possible to generate anatlantis.yamlfor only the affected component/s and this way limit the blast radius of a PR significantly.Alternatives Considered
parsing yaml until is not fun anymore....