This seems like it would be useful, however in practice I found the example at the bottom of the readme doesn't work since you can't use !ImportValue inside conditions.
I was wondering if you've found a way to get around this?
One thought I had would be to just use a template as a "re-exporter" if its not in the MasterRegion.
This might work, but you would still have to specify the MasterRegion in the parameters because you again can't import it into the condition.
Good work btw, I was looking for something exactly like this when I started to think about how Route 53 and IAM objects would be referenced in a region that didn't create them. Why AWS didn't make exports global is beyond me.
This seems like it would be useful, however in practice I found the example at the bottom of the readme doesn't work since you can't use
!ImportValueinside conditions.I was wondering if you've found a way to get around this?
One thought I had would be to just use a template as a "re-exporter" if its not in the MasterRegion.
This might work, but you would still have to specify the MasterRegion in the parameters because you again can't import it into the condition.
Good work btw, I was looking for something exactly like this when I started to think about how Route 53 and IAM objects would be referenced in a region that didn't create them. Why AWS didn't make exports global is beyond me.