-
Notifications
You must be signed in to change notification settings - Fork 209
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
test: add e2e test for odigos cli upgrade from latest to HEAD #1446
Conversation
fmt.Println("Odigos upgrade failed - unable to read the current Odigos version for migration") | ||
os.Exit(1) | ||
} | ||
if !cmd.Flag("skip-version-check").Changed { |
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.
the change here is adding this new flag since the current upgrade behavior requires a valid formatted version v1.2.3
while the tests use the tag e2e-test
. this flag allows the test to bypass the checks
spec: | ||
containers: | ||
- name: manager | ||
image: keyval/odigos-autoscaler:e2e-test |
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.
review note: i tested it locally once with an illegal tag value keyval/odigos-autoscaler:illegal
to make sure this is asserted correctly and it does
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.
looks great!
Since odigos upgrade is a potentially sensative process which can fail for various reasons, this PR adds an e2e test that starts with the latest odigos version from github, and then calls cli upgrade to the current version in HEAD.
Then it generates traffic and verify that traces are created.