-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat(acm)!: remove direct kubectl commands #1751
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. |
a9ebe65
to
7d5653f
Compare
fixed the docs |
/gcbrun |
@apeabody any update on this? would love to switch back to upstream :) |
/gcbrun |
@apeabody I've got some feedback on the kubernetes restart handler: hashicorp/terraform-provider-kubernetes#2304 (comment) Would you prefer to leave it as is, or should i update the PR for the recommended solution? I'm not really sure of the use of |
Hi @foosinn - This will be going into major version (#1746), so I would recommend including everything in this PR so any upgrade migration required is only one-time. It appears we already include the |
i'll update tomorrow to the recommended fix. Can you somehow share the log output of |
Failure appears unrelated (timeout), I've re-triggered the run. |
7a3a998
to
2c47ab6
Compare
Switched to the suggested solution and also rebased latest master. Let me know if you need anything else. Did also a quick test with our fork, seems to work fine :) |
From the linter
|
And again fixed the docs |
/gcbrun |
kubectl-wrapper currently breaks if one has to access the api using a proxy (IAP).
/gcbrun |
Can you share the error that happened? |
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 @foosinn
Marking as a breaking change given the config "churn" window.
/gcbrun |
thanks! |
…1751) Co-authored-by: Andrew Peabody <[email protected]>
kubectl-wrapper currently breaks if one has to access the api using a proxy (IAP).
This replaces the wrapper call for all annotations with the
kubernetes_annotations
resource. Thekubernetes
provider is already in use for the secret.In addition it allows the user to disable the automated restart. Sadly it's currently not possible to work around this AFAIK