-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix!: Don't provide defaults for public repositories #34
fix!: Don't provide defaults for public repositories #34
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
@prabhu34 - Got the CLA sorted out here. Would love to get this into the mainline so we don't have to maintain a fork. :) |
/gcbrun |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @frmrm!
Can you please rebase (or ideally add permission for maintainers).
Also, as this will be a breaking change, so we might need an upgrade guide similar to https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/blob/master/docs/upgrading_to_v33.0.md
(re-opening triggers the stuck lint workflow) |
/gcbrun |
From the lint test:
|
23c2f58
to
450503e
Compare
@apeabody I have rebased on the latest |
Do you want the upgrade guide additions as a part of the same commit or as a subsequent commit? |
I'd prefer everything in this PR, so we keep the repo aligned. Thanks! |
Here is the doc, but I believe some Orgs may restrict it: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork#enabling-repository-maintainer-permissions-on-existing-pull-requests |
That's probably the issue - our enterprise may have it set at the enterprise level and our OSS forks org is subject to that. |
@apeabody Updated. Let me know if that's what you're thinking or if further changes are needed. |
/gcbrun |
@apeabody Are you needing anything further from me on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @frmrm!
This PR drops the default values for the
public_repository
keys underremote_repository_config
. This fixes the underlying issue with configuring custom remote repositories, but it will require the data structures for folks using the public repositories to be a bit more verbose, unfortunately.closes #32