https://prefect.io
Join Slack
We recently upgraded from using the the builtin `GCS` class to the `GcsBucket` class from the `prefe...
# ask-community
a
We recently upgraded from using the the builtin 
GCS
class to the 
GcsBucket
class from the 
prefect-gcp
package to create the storage block for one of our prefect flow deployments since 
GCS
has apparently been deprecated. However, we're now seeing a strange issue when creating the deployment. The flow run code is being uploaded to a GCS bucket path that is a doubling of the bucket path configured on the 
GcsBucket
. For example, we'd expect the full path to the flow to be 
<gs://my-bucket/my-flow/v0.1.0>
but are seeing something like 
<gs://my-bucket/my-flow/v0.1.0/my-flow/v0.1.0>
. Are we configuring something wrong, or could this potentially be a bug?
n
hi @Adam Eury - this sounds like it could be related to this recent change (as in, you might be before this version) can you share which version of the 
prefect-gcp
lib you're using?
a
Hi @Nate! Thank you for the response. It looks like we're currently on 
0.5.12
.
n
okay, I think this is fixed in >=0.5.13
a
okay, I'll try it again after updating the version
Unfortunately it looks like that didn't help. These are the versions of prefect and prefect-gcp I just tried it with
Copy code
$ pip list | grep prefect
prefect                               2.16.9
prefect-gcp                           0.5.14
We're also currently still using the old way of building prefect deployments:
Copy code
prefect deployment build "..."
is it possible this contributing to the issue?
n
yes its possible. can you share the full command you use to deploy?
a
sure
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by