Status Update
Comments
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #2
gcloud config set app/use_gsutil true
ph...@gmail.com <ph...@gmail.com> #3
si...@google.com <si...@google.com> #4
Hello,
Thank you for the reply.
Could you please provide the full code and the minimum replication steps to further investigate the case on my end?
ph...@gmail.com <ph...@gmail.com> #5
[image: Screenshot from 2022-05-13 10-49-08.png]
/home/c4buckets/.local/bin/gcloud --format=json alpha pubsub
subscriptions pull $platine_subscription
--project=vg1np-apps-plagadm1-pre01-42 --wait --auto-ack >
/home/c4buckets/scripts_buckets_google_platine/messages/$platine_subsctiption_$$
fichier=$(cat
/home/c4buckets/scripts_buckets_google_platine/messages/$platine_subscription_$$
| /home/c4buckets/.local/bin/jq -r '.[] .message.attributes.objectId')
gcloud --format=json alpha pubsub subscriptions pull
$platine_subscription --project=vg1np-apps-plagadm1-pre01-42 --wait
--auto-ack >
/home/c4buckets/scripts_buckets_google_platine/messages/$platine_subsctiption_$$
fichier=$(cat
/home/c4buckets/scripts_buckets_google_platine/messages/$platine_subscription_$$
| /home/c4buckets/.local/bin/jq -r '.[]
.received_message.message.attributes.objectId')
On Fri, May 13, 2022 at 10:25 AM <buganizer-system@google.com> wrote:
si...@google.com <si...@google.com> #6
Hello,
The PubSub Engineering team has confirmed that this new message format only currently affects the 'gcloud alpha' and 'gcloud beta' commands which introduced the new --enable-exactly-once-delivery
property. This update of the received_message of the Pub/Sub message format change will be updated in the released notes. There is no ETA available for this.
ph...@gmail.com <ph...@gmail.com> #7
I need alpha for the -wait option.
Have a good day,
P.
On Thu, May 19, 2022 at 9:40 AM <buganizer-system@google.com> wrote:
si...@google.com <si...@google.com> #8
Hello,
If you need a new feature then please raise a feature request in the
ph...@gmail.com <ph...@gmail.com> #9
the situation will roll back ???
P.
On Tue, May 24, 2022 at 3:04 PM <buganizer-system@google.com> wrote:
si...@google.com <si...@google.com> #10
Hello,
-
The engineering team has confirmed that the change in format will be backward compatible, so that both the formats
.received_message.message.attributes.objectId
and.message.attributes.objectId
can be used. -
They will Fix the backward compatibility for gcloud pull json format response and will also add the json format unit tests for gcloud pubsub subscriptions pull.
ph...@gmail.com <ph...@gmail.com> #11
So it is good for me.
si...@google.com <si...@google.com> #12
Hello,
Since you have confirmed that the issue is resolved, I am marking this issue as fixed.
However, if you still face any issue, please don’t hesitate to raise a new thread describing the issue.
Description
I have noticed a change in the event message structure.
I need to use ".received_message.message.attributes.objectId". to reach objectid on 375.
on 374 it was ".message.attributes.objectId"
Didn't find any notice or documentation about this change.
Is it normal???
Have a good day,
P.