Add base_name var and use it#495
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #495 +/- ##
===========================================
- Coverage 51.05% 22.63% -28.42%
===========================================
Files 11 28 +17
Lines 903 1975 +1072
===========================================
- Hits 461 447 -14
- Misses 374 1451 +1077
- Partials 68 77 +9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Can you explain why? I don't see anything breaking here, but it makes a few minor ergonomic regressions. The base name seems to get used directly for naming different resources, without any suffix. I don't think this causes a problem because each resource type is a different namespace, but it was nice that the service was |
The driver is to enable multiple instances to be deployed in the same project. Spanner display name I'd have happily removed and left unset, but it's only there because it's a required field. Dropping |
mhutchinson
left a comment
There was a problem hiding this comment.
Sure, as long as it's intentional. I guessed this was the intent, but raised a yellow flag because base_name implied it was to be built on. Go ahead!
Good call, thanks for checking! |
This PR introduces a base_name variable to the witness terraform module, and uses it when naming resources it creates.
This allows for deploying multiple independent instances within the same project.