Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

EVEREST-386: backup name is required #134

Merged
2 commits merged into from
Sep 13, 2023
Merged

Conversation

ghost
Copy link

@ghost ghost commented Sep 12, 2023

Copy link
Contributor

@gen1us2k gen1us2k left a comment

Choose a reason for hiding this comment

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

Can we have integration tests for those two bugs? It looks like we have everything to that. WDYT?

Copy link
Collaborator

@recharte recharte left a comment

Choose a reason for hiding this comment

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

Changes look good, waiting for an answer to Andrew's comment before approving and also throwing a question myself.

pkg/install/operators.go Show resolved Hide resolved
@ghost
Copy link
Author

ghost commented Sep 12, 2023

Can we have integration tests for those two bugs? It looks like we have everything to that. WDYT?

I personally don't think this is worth adding an integration test for.
Happy to add it though if you think it is.

@ghost ghost enabled auto-merge (squash) September 12, 2023 13:44
@gen1us2k
Copy link
Contributor

Happy to add it though if you think it is.

How can we ensure that it works? I think that adding backups should be stable and covered by integration tests so we will be sure during the time that it's covered and it works so we do not need to spend time to re-test it during the release

@ghost
Copy link
Author

ghost commented Sep 12, 2023

How can we ensure that it works? I think that adding backups should be stable and covered by integration tests so we will be sure during the time that it's covered and it works so we do not need to spend time to re-test it during the release

Tests added.

@ghost ghost merged commit c3e3814 into main Sep 13, 2023
8 checks passed
@ghost ghost deleted the EVEREST-386-backup-name-required branch September 13, 2023 07:08
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants