-
Notifications
You must be signed in to change notification settings - Fork 788
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
wip: fix: Get Velero Azure plugin operational #7451
wip: fix: Get Velero Azure plugin operational #7451
Conversation
Hi @chrismellard. Thanks for your PR. I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Related jenkins-x-boot-config PR here jenkins-x/jenkins-x-boot-config#168 |
af67b8e
to
28c81d9
Compare
62bc947
to
15e49ee
Compare
00ba3f0
to
dfe1cf9
Compare
I know the codebase does not have good test coverage, but would be nice if you can add some tests for the code u wrote. |
Also, you should squash your commits, and run |
Thanks. Left the two commits in there as they were addressing different concerns - kinda. But happy to squash them up with addressing your feedback. Try get something turned around tonight. |
2f9d4ff
to
7bfeb92
Compare
/ok-to-test |
2584f07
to
253461f
Compare
/retest |
1 similar comment
/retest |
I think you should rebase this PR with the latest master, there was a PR which fixed issues with builds: #7460 @chris-mellard |
253461f
to
64f80b0
Compare
🤷 |
35b6b2f
to
9b3d0f7
Compare
65853ed
to
d76fa07
Compare
this is the unit test failure:
|
The boot and terraform BDD tests are failing to deploy a quickstart into the staging environment, the staging master pipeline has the following error:
|
@chrismellard looking at the PR is it fair to say it provides a way to create buckets in azure storage? I wonder if this should be done as part of Terraform instead. There has been an effort of work this year to decouple and move the creation + management of cloud resources out of the jx CLI and into Terraform. I wonder if that would be a better approach? What would be the main challenges doing that? In the future we'd like to support other means of creating clusters too, https://crossplane.io/ looks really interesting as well but the more we can decouple cloud provider related commands from core jx the easier things like that will be. WDYT? |
Unit test appears to have been failing for a while and I'm fixing up in another PR, seems to be related to git error messages based on empty commits for rebases vs cherrypicks... though surprised given this PR contains that fix this is still failing unit tests (it certainly rectifies a unit test failure locally) Happy to move these cloud resource creations in to terraform. Was unaware of the initiative to move this logic in to terraform ;) I'll have a think and revise this PR (+ terraform module) |
Ok sounds good, we need to do a better job of communicating these initiatives, I'll add an agenda item for the office hours next week to discuss ways we need to improve. |
Unit test PR here btw - #7468 |
Having thought about this and with a view to not break other public cloud implementations how about we create a structure of cloud capabilities per cloud cluster, i.e. what we are or are not leveraging from terraform modules. Can start to data drive the code from this rather than hard coding Does that sound like an approach everyone is happy with? Second question - are we happy to hard code this terraform capability structure in code - doesn't seem to be any benefit to me to externalise this logic. |
/retest |
…n operational Encapsulated the storage account parsing down close the CLI which appears to be the only part that requires them as separate arguments ... to get Velero boot operational Signed-off-by: Chris Mellard <[email protected]>
d76fa07
to
514f755
Compare
@chrismellard: The following tests failed, say
View all Builds for this Pull Request Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. |
Will reopen another PR for this when it's nearer completion |
Submitter checklist
Description
Adds in new requirementsConfig keys to support Azure Velero plugin. Further changes required to be made to boot repo. Need to implement part of the BucketProvider interface to get through the boot process. Only those methods required to get through
jx boot
implemented for nowSpecial notes for the reviewer(s)
Which issue this PR fixes
fixes #7450