Skip to content

Conversation

@Tybot204
Copy link
Contributor

@Tybot204 Tybot204 commented Feb 20, 2025

What

Issue: airbytehq/airbyte#54176

Current Helm values.yml documentation and defaults have old unused values for externalDatabase, potentially leading to confusion when setting up or upgrading Helm chart versions.

How

This removes externalDatabase from all defaults and documentation. These values are not used anywhere in the project outside of the changes files in this PR. Instead global.database should be used instead to configure external PostgreSQL connections.

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

@CLAassistant
Copy link

CLAassistant commented Feb 20, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Tybot204
❌ perangel
You have signed the CLA already but the status is still pending? Let us recheck it.

@marcosmarxm
Copy link
Contributor

cc @airbytehq/platform-deployments

@perangel
Copy link
Contributor

/create-oss-pr

@perangel perangel merged commit 728d18d into airbytehq:main Feb 28, 2025
4 of 5 checks passed
Conall-airbyte pushed a commit that referenced this pull request Jun 4, 2025
## What
<!--
* Describe what the change is solving.
* It helps to add screenshots if it affects the frontend.
-->

Issue: airbytehq/airbyte#54176

Current Helm `values.yml` documentation and defaults have old unused
values for `externalDatabase`, potentially leading to confusion when
setting up or upgrading Helm chart versions.

## How
<!--
* Describe how code changes achieve the solution.
-->

This removes `externalDatabase` from all defaults and documentation.
These values are not used anywhere in the project outside of the changes
files in this PR. Instead `global.database` should be used instead to
configure external PostgreSQL connections.

## Can this PR be safely reverted and rolled back?
<!--
* If you know that your be safely rolled back, check YES.*
* If that is not the case (e.g. a database migration), check NO.
* If unsure, leave it blank.*
-->
- [x] YES 💚
- [ ] NO ❌

Co-authored-by: perangel <[email protected]>
Conall-airbyte pushed a commit that referenced this pull request Jun 23, 2025
## What
<!--
* Describe what the change is solving.
* It helps to add screenshots if it affects the frontend.
-->

Issue: airbytehq/airbyte#54176

Current Helm `values.yml` documentation and defaults have old unused
values for `externalDatabase`, potentially leading to confusion when
setting up or upgrading Helm chart versions.

## How
<!--
* Describe how code changes achieve the solution.
-->

This removes `externalDatabase` from all defaults and documentation.
These values are not used anywhere in the project outside of the changes
files in this PR. Instead `global.database` should be used instead to
configure external PostgreSQL connections.

## Can this PR be safely reverted and rolled back?
<!--
* If you know that your be safely rolled back, check YES.*
* If that is not the case (e.g. a database migration), check NO.
* If unsure, leave it blank.*
-->
- [x] YES 💚
- [ ] NO ❌

Co-authored-by: perangel <[email protected]>
Conall-airbyte pushed a commit that referenced this pull request Sep 17, 2025
## What
<!--
* Describe what the change is solving.
* It helps to add screenshots if it affects the frontend.
-->

Issue: airbytehq/airbyte#54176

Current Helm `values.yml` documentation and defaults have old unused
values for `externalDatabase`, potentially leading to confusion when
setting up or upgrading Helm chart versions.

## How
<!--
* Describe how code changes achieve the solution.
-->

This removes `externalDatabase` from all defaults and documentation.
These values are not used anywhere in the project outside of the changes
files in this PR. Instead `global.database` should be used instead to
configure external PostgreSQL connections.

## Can this PR be safely reverted and rolled back?
<!--
* If you know that your be safely rolled back, check YES.*
* If that is not the case (e.g. a database migration), check NO.
* If unsure, leave it blank.*
-->
- [x] YES 💚
- [ ] NO ❌

Co-authored-by: perangel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants