We always use the same directory for terraform fixtures, so it's quite
easy to figure out its path from a pytest fixture by inspecting the
stack. This commit implements this functionality and decreases the
amount of boilerplate needed to write a test.
(Ported from fast)
* Cloud DNS and Shared VPC (#184)
* Cloud DNS and Shared VPC module to allow application teams to have their own Cloud DNS configuration.
* Cleaning up README.md
* Improving Formating.
* Adding license to all .tf files.
* Removing dead code.
* Moving this example into the Cloud Operations folder.
* Using fabric resources and refactoring. Only the 'test.example' file is not using the proper modules now.
* normalize README, use autogenerated vars table, add types to variables
* refactor
* simple tests
* add diagram, update READMEs
Co-authored-by: Aurélien Legrand <aurelien.legrand01@gmail.com>
* add missing role to GKE nodepool service account
* refactor plan test runners
* remove spurious print statements from test
* use concurrency via locking the fixture dir
* add filelock to test requirements
* fix pytest arg in cloud build
* and yet another dep and args fix
* fix e2e runner, use correct runner in env e2e test
* revert parallel test changes, split modules and environments triggers
* I should stop experimenting in PRs
* first working example for asset inventory feeds
* move tf files out of the tf folder
* add input/outputs to README
* smaller diagram
* use narrow scoped service account for cf, account for gke tags in code
* Update README.md
* new top-level folder README
* Update README.md
* add TODO for DNS example in operations README
* fix README conflict
* Update README.md
* Update README.md
* update diagram
* cloud shell
* cloud shell
* Update README.md
* rename outputs, first complete README draft
* Update main.py
* Update README.md
* Update README.md
* better error handling in the cloud function
* remove branch from cloud shell link
Ludovico Magnocavallo
Simone Ruffilli
Julio Castillo
Mikołaj Stefaniak