SameerMesiah97 commented on PR #61527: URL: https://github.com/apache/airflow/pull/61527#issuecomment-3874724051
> in opotion 2, i did not add it, but it would go like > > * airflow.apache.org/connection-name > * airflow.apache.org/variable-name > * airflow.apache.org/config-name > > as per maintainig uniquness on secrets/labels, this is not a backend role to maintain proper secrets deployment, secrets backend reads connections, if the connections are wrongly deployed to a namespace this is a totally different problem (this is how I see it ) I agree with you. I think it should be the user’s responsibility to enforce secrets/labels uniqueness. But is it possible for your new secrets backend to detect duplicate secret configurations (by name) and log a warning? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
