Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

astro dev object import ignores conn_extras field #1591

Open
1 of 3 tasks
zach-nicoll-wcq opened this issue Mar 8, 2024 · 1 comment
Open
1 of 3 tasks

astro dev object import ignores conn_extras field #1591

zach-nicoll-wcq opened this issue Mar 8, 2024 · 1 comment
Assignees

Comments

@zach-nicoll-wcq
Copy link
Contributor

Describe the bug

Our airflow_settings.yaml file contains connections that make use of the conn_extra field (we are using the aws connection type).

However, when attempting to import these values into the UI via astro dev object import, the conn_extra field is ignored and the key/value pairs are not uploaded.

The terminal output makes no indication that something has gone wrong:

astro dev object import
Updating Connection "athena-transformed-dev"...
Added Connection: athena-transformed-dev
Updating Connection "athena-trusted-dev"...
Added Connection: athena-trusted-dev

What CLI Version did you experience this bug?

1.24.1

This CLI bug is related to which Astronomer Platform?

  • Astro
  • Software
  • None/Unknown

What Operating System is the above CLI installed on?

  • MacOS
  • Nobara (Fedora) Linux

🪜 Steps To Reproduce

  1. Create an airflow_settings.yaml file that looks like this:
airflow:
  connections:
  - conn_extra:
      aws_session_token: some_token
      role_arn: some_role
    conn_id: conn_1
    conn_login: some_login
    conn_password: some_password
    conn_type: aws
  - conn_extra:
      aws_session_token: some_token
      role_arn: some_role
    conn_id: conn_1
    conn_login: some_login
    conn_password: some_password
    conn_type: aws
  1. Run astro dev object import
  2. Observe the 'Extra' field to be an empty JSON object

📸 Screenshots

image

@sunkickr
Copy link
Contributor

@zach-nicoll-wcq the extra field could be just hidden in the UI. Can you tell if the extra field is actually not there when running the DAG?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants