Closed rawwar closed 4 months ago
@rawwar Has environment secrets fetching been enabled on the organization, per these docs?
Member
yes, its enabled. I think there's some issue with parsing the extra field. Otherwise, using a simple JSON like {'test':'hello_world'}
in extra wouldn't work.
The fix was released in 1.25.0
Describe the bug
I created a Connection of type "Google Cloud Platform" using "Generic" on Astro Cloud UI. Following are the steps to replicate the creation
On Astro:
Once the connection is created and linked with the deployment, Exec into the worker pod and run
airflow connections get gcp_test_2
. This will return the following.In Local:
I followed the following article for running a local deployment - Link
Commands to start the env:
Now, exec into a container(I've exec'ed into scheduler) and run
airflow connections get gcp_test_2
Command returns the following:extra_dejson
is empty in local. Also, we can see a warning saying that the astro managed secrets backend is disabled`I have tested the above for simple JSON data in extra field like
{"test":"hello"}
and for this case, I can see similar results in local and in astro env. But, when giving Google Cloud's keyfile json data, this issue is happening.What CLI Version did you experience this bug?
Astro CLI Version: 1.24.1
This CLI bug is related to which Astronomer Platform?
What Operating System is the above CLI installed on? IOS