Thought I'd report this here as I'm very unsure where one might report bugs.

SUMMARY
Once a VPC configured inside an Environment it will not refresh or reload 
easily.

DETAIL
In 5.8.29 I created an Environment and them a Farm that I set to use a VPC. 
 I then noticed that my both subnets in my VPC were marked at "private" 
which is was a mistake on my part.  I went back into AWS and changed the 
subnet so that it had a default (0.0.0.0/0) route to a gateway, but on 
returning to the Farm my VPC was still marked as "private". 

I tried creating another Farm with the same results.  The VPC was still 
cached as "private"

WORKAROUND
What did was was to create a new Environment and a new Farm in that 
Environment.  This appears to trigger a refresh of the VPC data and the AWS 
changes were now visible.  I'm curious is there is a better way to refresh 
settings.

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to