Aaron ("AJ") Steers

Closing this one out as stale. We have since moved to a different approach for airflow. fyi @DouweM - feel free to reopen if this is still needed.

@cjohnhanson - re: > Do we necessarily want to treat secrets that differently than other settings? One approach to this would be to just implement secrets backends as SettingsValueStores. I've...

2 known challenges: ## Challenge 1: How to map arbitrarily named keys in the setting store to specific settings The external parameter store may be controlled by another team besides...

From Cody: > Airflow also has some prior art here that could be a good reference as we're thinking through this: https://airflow.apache.org/docs/apache-airflow/2.3.2/security/secrets/secrets-backend/index.html

Closing as `duplicate`, in favor of: - https://github.com/meltano/meltano/issues/2982 - https://github.com/meltano/meltano/discussions/6879 - https://github.com/meltano/dragon-infra/discussions/34

Unassigning, as this should be resolved by: - #3419 - #6116 - #6247 After those are resolved, we should revisit to see it this is still an issue.

Agreed I think the simple path is best, to simply remove the equivalence check and _always_ do a set when a set operation is requested. If the user wants a...

Asking the inverse: Should we internally disallow `RENAME COLUMN` operations within Alembic migrations in our contributing guide and for internal operations? Perhaps even a CI test that searches the alembic...

@WillDaSilva - Thanks for your work to proactively invest in cleaner and leaner build processes. What the process doesn't really give us in this iteration is what actions we'd take...

@cjohnhanson - Great - thanks for looking into this! I've assigned to you in next iteration but also okay if you have time to pick up this week.