Juri Rischel Jensen

@torgebauer I face the same issue, but have no PVC's at all. For me it's related to namespace deletion. It might be that TF is trying to delete the namespace...

Yes - sure! Here it is (some output is obfuscated): ``` [DEBUG ] Running install command... [INFO ] Installing dependencies: production [DEBUG ] Searching for config... [DEBUG ] Looking for...

Yes, sure: ```yaml location: .gitman sources: # Production sources - name: module-production link: modules/module1 repo: [email protected]:username/gitman-submodule.git rev: 1.0.0 # Dev sources - name: module-sandbox link: modules/module1 repo: [email protected]:username/gitman-submodule.git rev: master...

Hi Jace Thank you for your answer. You’re right that I can used locked_sources for that simple example. Truth is that I have 3 environments - production, preprod and prod...

Hi Jace Thank you for the pointers - I’ll have a look at it. Gitman files without groups: Maybe just treat that as a normal gitman install, and install the...

@daniel-brosche Thank you for your input - although I have a hard time figuring out what you are doing. Can you maybe paint the picture a little bit clearer with...

This is almost how I do it. I have a directory structure like this one: ``` tf-live/ ├── gitman.yml ├── tf-bootstrap │   └── modules │   └── tf-aws ├── tf-network │  ...

Just a quick thought: Would it be possible/nice to structure the config as follows, instead of the separate groups section?: ```yaml location: .gitman sources: default: # Production sources - name:...

I've come up with an alternative approach that I like a bit better. First we add a gitman config file for each environment: gitman-production.yml gitman-preprod.yml gitman-sandbox.yml Then a simple Makefile:...