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

Rename family parent package from provider-gcp-config to provider-family-gcp #305

Merged
merged 1 commit into from
May 16, 2023

Conversation

ulucinar
Copy link
Collaborator

@ulucinar ulucinar commented May 16, 2023

Description of your changes

This PR proposes a renaming of the family parent package from provider-gcp-config to provider-family-gcp.

I have:

  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Validated in crossplane-contrib/provider-upjet-azure#452.

@@ -23,6 +23,6 @@ metadata:
{{ if and (ne .Service "config") (ne .Service "monolith") -}}
spec:
dependsOn:
- provider: {{ .XpkgRegOrg }}/provider-{{ .ProviderName }}-config
- provider: {{ .XpkgRegOrg }}/provider-family-{{ .ProviderName }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe we should also update the label value

Copy link
Collaborator Author

@ulucinar ulucinar May 16, 2023

Choose a reason for hiding this comment

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

Thanks for the catch. We had better parameterize the family parent repo name at some point I guess :)

…ily-gcp

Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
Copy link
Contributor

@ezgidemirel ezgidemirel left a comment

Choose a reason for hiding this comment

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

Thanks @ulucinar :)

@ulucinar ulucinar merged commit d560a83 into crossplane-contrib:main May 16, 2023
9 checks passed
@ulucinar ulucinar deleted the rename-config-package branch May 16, 2023 13:44
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.

None yet

2 participants