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

chore: remove unneeded reference to legacy registry setting #3659

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

shreddedbacon
Copy link
Member

General Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for inclusion in changelog

Database Migrations

  • If your PR contains a database migation, it MUST be the latest in date order alphabetically

Just removes an unneeded reference to a registry. This variable is not consumed by anything in core beyond passing it through to the remote. The usage of this is from a historical perspective, it was used when Lagoon didn't have support for harbor in core, or harbor in remote.

It isn't related to the legacy harbor implementation in core either as these provide variables to the project in the form of INTERNAL_REGISTRY_X which get added to the build payload when it sent to a remote. The legacy harbor implementation in core is planning to be removed (#2907 , #3259, and others) and was announced as deprecated in v2.17.0

Closing issues

closes #2238

Copy link
Member

@tobybellwood tobybellwood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

straightforward enough

@tobybellwood tobybellwood merged commit 82725d0 into main Feb 29, 2024
1 check passed
@tobybellwood tobybellwood deleted the remove-legacy-registry branch March 13, 2024 01:45
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.

improve usage of REGISTRY env variable
2 participants