Thanks for the suggestion, this is an interesting idea, we’ll consider it!Jules Lefevre shared this idea ·
Hi folks, we know there is a ton of interest in this ability, and our engineering team is working on enabling it. We don’t have specific schedule updates right now, but I wanted to post an update acknowledging that we definitely agree this is an important ability and we will launch the functionality just as soon as we can!
Paul, we appreciate the new update - to learn this is not an easy implementation is news, prior to this support had only agreed with us that "it does seem trivial" - leaving a lot to be wondered.
Looking forward to further updates.
@Steve Larson, sadly mate snapshotting does not retain metadata etc. All of this information does have to be re-entered manually.
4 years onwards and... Seriously, nothing.
I genuinely was astounted when I found there was not a way to rename VM's back in 2014. It's easy to say "Yes, you're right, it's trivial", but truly Paul, this is so far beyond "Trivial" that it's actually embarrassing to admit to my AWS supporter friends that "Yes you STILL can't rename VM's in GCP".
I can't believe this has gone this long without it's due attention. It's the 4th highest requested feature currently on GCE, and let's be honest, an intern with a day's free time could have had this solved all too long ago.
At the end of the day, if it takes 4 years to fix something "trivial" then perhaps the method in which issues are deemed worthy of fixing should be "fixed".
Interesting idea, we’ll consider it – thanks!
We appreciate all of your feedback on how critical the HTTP→HTTPS redirect feature is to your GCP apps. Our networking team has further increased the priority of this feature in our backlog based on your feedback and are aiming to deliver an Alpha in Q4, 2019.