[google-appengine] Re: Not able to list images in GCR

['Darrell (Cloud Platform Support)' via Google App Engine]

Hi,

I understand that you want to list list the images from cloud shell and you 
have 5 images. You are correct that you can list the existing images with 
the "gcloud container images list --repository=" command[1]. However, 
I think you should omit the "2.0" from the "repository" flag as I believe 
that "gcr.io/projectid/repo-name/2.0" is the image name. 
*$ gcloud container images list --repository gcr.io/projectid/repo-name*

However, if you are looking to list the tags and digests for the "2.0" 
image, you can use the "gcloud container images list-tags" command[2].
*$ gcloud container images list-tags gcr.io/projectid/repo-name/2.0*

I hope you'll find information provided above useful.


[1] 
https://cloud.google.com/sdk/gcloud/reference/container/images/list#--repository
[2] https://cloud.google.com/sdk/gcloud/reference/container/images/list-tags

On Monday, November 8, 2021 at 2:46:55 PM UTC-5 ravia...@gmail.com wrote:

> Hi, 
> raviatloop@cloudshell:~ ()$ gcloud container images list --repository=
> gcr.io/projectid/repo-name/2.0
> Listed 0 items.
> raviatloop@cloudshell:~ ()$
>
> I am not able to list the images from cloud shell even there are around 5 
> images exits in the gcr.io/projectid/repo-name/2.0
>
> Thanks for the help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/425c3ab0-ccb6-477d-a262-59eeb82c8a59n%40googlegroups.com.

Re: [google-appengine] Re: Updates from the Google App Engine team (Fall 2021)

['Alex Martelli' via Google App Engine]

On Mon, Nov 8, 2021 at 10:47 PM Kaan  wrote:
   ...

> And a plug: Python in my opinion is dying, while JS / NodeJS is thriving
>

According to TIOBE , in October Python
was language #3 in terms of popularity (behind Java and C); in November, it
vaulted to first place, "end[ing] C and Java's 20-year reign atop the TIOBE
index" as TechRepublic

titled their article -- "just one more feather in Python's ever-plumier
hat", as their subtitle has it, and "Python's latest win is just another in
its long line of toppling long-standing language leaders", as they write in
the body of the article (Python is also the most popular programming
language according to the IEEE study
, the most "wanted"
language according to StackOverflow's survey
,
the "AI lingua franca" according to datanami
,
and so forth). Javascript is #7 on TIOBE's list and #5 on the IEEE's, by
the way.

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAE46Be_EEYQnxOec1r61ZHCo%3DifO__vO7%2Bf1i2BHpB8hL0RuUg%40mail.gmail.com.

Re: [google-appengine] Re: Updates from the Google App Engine team (Fall 2021)

[Walt Pang]

In data science industry most people are still using python as development
tool.

Kaan 于2021年11月9日 周二下午2:47写道：

> Honestly this is all very exciting, and like you've also pinpointed the
> main issue, we were (I was!) blind to the most important of changes,
> there's so much segmentation now that what's actually important goes
> missing in all the noise
>
> *1)* *Dev App Server is a thing again?!*
> https://cloud.google.com/appengine/docs/standard/python3/tools/using-local-server
> *2) *The backwards compatibility update:
> https://cloud.google.com/blog/products/serverless/support-for-app-engine-services-in-second-generation-runtimes
>
> Honestly I haven't tried the new to me dev app server yet, but I'm finally
> in theory ready to go from Python2 to Python3! But as Will Reiher pointed
> out, for a more complex project, there are still icky details like the
> blobstore, images api etc. - so for "legacy legacy" projects, I'd not
> attempt it and sunset them instead
>
> And a plug: Python in my opinion is dying, while JS / NodeJS is thriving,
> consider bringing emulators into the JS ecosystem too and also please
> invest some effort into code/api design, it seems to me that someone is
> just translating libraries from Python to JS and releasing it as it is
>
> On Tuesday, November 9, 2021 at 3:53:27 AM UTC+3 Will Reiher wrote:
>
>> Hi,
>>
>> Thanks for the follow up. The articles detail the process fine if the
>> underlying blobs are "on" cloud storage. In my case I'm talking about
>> legacy blobs stored outside of the my visible buckets. They're not
>> represented in cloud storage and the python 3 runtime does not seem to have
>> a way to access them from what would be the remaining blobkey references.
>> From my understanding my legacy blobs would not have a corresponding
>> "gs_object_name" that would facilitate me accessing them. That is also very
>> much moot on the new runtime since it doesn't provide the BlobInfo api
>> where I would be able to access the gs_object_name property.
>>
>> I have a feeling the new "appengine-python-standard" library will provide
>> a partial answer as it looks like it will expose some of the old Blobstore
>> APIs that I would need to continue to access legacy blobs that are not
>> listed in an assessable bucket.
>>
>> The new library still seems to be missing the BlobstoreDownloadHandler
>> that would allow the end user to be redirected to download the file. This
>> basically set a header and the platform would deliver the blob to the
>> client.
>> On Monday, November 8, 2021 at 1:55:41 PM UTC-8 amit...@google.com wrote:
>>
>>> Hi,
>>>
>>> I believe you are referring to this
>>> 
>>> for python 2. While taking a look into this , I have found two stack
>>> overflow posts recommending to use Cloud Storage here
>>> 
>>> and here
>>> 
>>>  while
>>> using python 3. You can check if any of those fits into your use case.
>>> On Monday, November 8, 2021 at 12:38:40 PM UTC-5
>>> will@friesenpress.com wrote:
>>>
 I'm slowly moving my way towards a migration path to the new Python 3
 runtime. 2022 is the year. I've been a AppEngine customer since 2009 - so
 I've already seen my share of smaller migrations as the oldest of the
 services died off.

 I currently have a question about Blobstore. As I'm planning to
 decouple services in preparation for the first of many migrations I'm
 wondering about all my old blobs. All my new blobstore files, as of summer
 of last year, are in the default cloud storage bucket and I'm keeping track
 of the "gs_object_name" so that they'll continue to be easy to work
 with as I migrate which is nice.

 The real question is after I move my apps to the Python3 runtime how
 will I access my legacy blobs? I see that cloud NDB "supports" blobkeys and
 I currently I'd use "blobstore_handlers.BlobstoreDownloadHandler" and
 "send_blob" to allow my users to download their files. I literally have a
 decade of stored blobkeys that I would like to be able to service after I
 move to the new runtime. I see that "send_bob" puts the blobkey in a header
 which I assume is picked up by the platform to deliver the file to the end
 user. Please point me in the right direction if you can!

 On Thursday, November 4, 2021 at 7:47:52 AM UTC-7 Wesley C (Google)
 wrote:

> App Engine and Google Cloud serverless users:
>
> The App Engine  team at Google
> Cloud  had a flurry of announcements and
> product updates over the past few months. In case you missed them, we've
> summarized them here with relevant 

[google-appengine] Re: Entities not showing in DataStore

['Felipe Bergallo Corral' via Google App Engine]

Are they visible if you query by GQL? Are they visible inside the 
application (or script, rather)? How are these entities being defined?

On Wednesday, November 3, 2021 at 12:09:46 PM UTC+1 fra.m...@gmail.com 
wrote:

> My Python 2.7 script runs smoothly. It was deployed first time in 2012 on 
> App Engine. 
> It defines and uses some datastore entities , creates entites and select 
> using GQL.
> Unfortunately such entities are not visible on the Google Cloud DataStore 
> browser, what's wrong? Under 'Kind' i can only see system tables
>
> [image: Cattura.PNG]
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3c64abca-f2b3-4e47-ab70-b51f3adcd095n%40googlegroups.com.