Conversation
|
This looks as though it might make all logs available on all provided subdomains(?) While it's probably fiiiiiiine, it does kinda seem a little against the grain of
and
Which doesn't really leave much space for having multiple submission prefixes. Maybe another way would be to make the |
|
Right, that's the "description" that I forgot to write :) This is meant to be temporary for as long as we have logs with different origin suffixes in a single project. I did consider writing a map, but concluded it was not worth it since this will all go away at some point. True that in the meantime each log will have two submission prefix, but as long as you don't share / use the "other one", everything is still specs compliant. I've left a TODO for now in the interest of moving faster, but I'm happy to implement the map solution if you think if you have more faith in code than promises to fix TODOS 🙄. |
I will leave it between you and your conscience :) |
c52d10b to
c120246
Compare
|
Done PTAL. |
| type = string | ||
| type = map(object({ | ||
| region = string | ||
| submission_host_suffix = string |
There was a problem hiding this comment.
As discussed IRL - maybe we could change this to submission_domain and add the . on L21 of loadbalancer/external/main.tf?
I think that might be a bit clearer on what's expected.
There was a problem hiding this comment.
Also added variable validation.
No description provided.