Add Integration Tests for Kopia RepositoryServer based kando Blueprint for MySQL#2026
Add Integration Tests for Kopia RepositoryServer based kando Blueprint for MySQL#2026
Conversation
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
|
Thanks for submitting this pull request 🎉. The team will review it soon and get back to you. If you haven't already, please take a moment to review our project contributing guideline and Code of Conduct document. |
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
…pia-repo-server-functions # Conflicts: # pkg/kopia/command/storage/storage_args.go # pkg/secrets/repositoryserver/const.go # pkg/testing/integration_register.go
| } | ||
|
|
||
| func (mdb *KopiaRepositoryServerMysqlDB) Chart() *helm.ChartInfo { | ||
| return &mdb.chart |
There was a problem hiding this comment.
Is retiring a pointer to the internal field desired? This might lead to external changes that could be potentially undesired here. WDYT?
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
| // DefaultKopiaRepositoryServerAdminPassword is the default password for the kopia repository server admin user. | ||
| DefaultKopiaRepositoryServerAdminPassword = "admin1234" | ||
| ) | ||
|
|
There was a problem hiding this comment.
@r4rajat this file contains lot of redundant code that pkg/testutil/testutil.go has. Should we reuse the functions in that file wherever possible?
| s.kopiaRepositoryServer.repositoryServer.Spec.Server.TLSSecretRef = corev1.SecretReference{ | ||
| Name: tls.GetName(), | ||
| Namespace: tls.GetNamespace(), | ||
| } |
There was a problem hiding this comment.
Should we move creation of secrets to another function? We are currently using s3 as a profile, but we have to write integration tests for other profiles such as filestore as well. In that case if creation of secrets is made generic, that would be useful
|
This PR is marked as stale due to inactivity. Add a new comment to reactivate it. |
|
This PR is marked as stale due to inactivity. Add a new comment to reactivate it. |
Change Overview
Add Integration Tests for Kopia RepositoryServer based kando blueprint for MySQL
Pull request type
Please check the type of change your PR introduces:
Issues
Test Plan
Manual Testing
1) Deploy Kanister
2) Change target of integration-test in makefile
3) Install minio
4) Run Integration Tests