#geodesic (2021-12)
Discussions related to https://github.com/cloudposse/geodesic
Archive: https://archive.sweetops.com/geodesic/
2021-12-21
![Andres avatar](https://secure.gravatar.com/avatar/3fda360d5572a1bbdd065a176fab54d7.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0008-72.png)
Hi guys, does the workflow exist in the new version of atmos (or are there plans to add it back in)?
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
@Andriy Knysh (Cloud Posse) plans to add it back
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
We have not deprecated it but it didn’t make its way into the new version
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
Partially because we wanted to make it more powerful
![Andriy Knysh (Cloud Posse) avatar](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)
![Andres avatar](https://secure.gravatar.com/avatar/3fda360d5572a1bbdd065a176fab54d7.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0008-72.png)
Sounds great, thank you!
![Andres avatar](https://secure.gravatar.com/avatar/3fda360d5572a1bbdd065a176fab54d7.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0008-72.png)
@Andriy Knysh (Cloud Posse) in terms of stacks, what would you say would be the “best practise” when it comes to creating stacks?
Should we put all resources in a single stack file or should we break them up into more manageable logical stacks?
If we should break up larger stacks into smaller pieces how to we then orchestrate creating them in the right sequence ? (shell script comes to mind)
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
we break our stacks into logical ones based on region and account
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
e.g. uw2-prod.yaml
would be one stack
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
if using gitops, the smaller the stack configs, the easier it is to detect changes to a smaller subset of the stack
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
the larger the stack configuration, the more stacks will need to be planned
![Mauricio Wyler avatar](https://avatars.slack-edge.com/2021-08-16/2386845713650_ebf28023ef9d5b2a28fc_72.jpg)
Hi any update on adding the workflows again? Meanwhile what would be a workaround? To use 0.21.3 version?
THANKS
![Andriy Knysh (Cloud Posse) avatar](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)
we are working on it
![Andriy Knysh (Cloud Posse) avatar](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)
the workaround would be to create a shell script and call atmos commands one by one - that’s actually what the workflows were doing and the new workflows will be doing as well
![Mauricio Wyler avatar](https://avatars.slack-edge.com/2021-08-16/2386845713650_ebf28023ef9d5b2a28fc_72.jpg)
OK! I imagen I had to do something like that! Thank you.
![Andriy Knysh (Cloud Posse) avatar](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)