-
Notifications
You must be signed in to change notification settings - Fork 14
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(develop): outbound-only new service flow #1050
base: master
Are you sure you want to change the base?
Conversation
e2e/fundamental_use_cases_test.go
Outdated
|
||
When("deploying new version of the service to the cluster", func() { | ||
|
||
It("should deploy new instance of the service and make it reachable through special route", func() { |
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.
Should we reword these to "deploy updated instance/version" instead of using "new" to not confuse with "new service" ?
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.
My thinking here was that I'm deploying new service, but I agree it should be reworded. I'll take care of it.
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.
Does it sound better now? bf7471e
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.
Not seeing the relevance? :)
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.
I think that should be more relevant: f31d18c
true is anyway default value to return so no need to evaluate this condition
Tests are poluting logs too much anyway. Default mode logs details on failures. In order to use verbose mode you can use `make test -v`
Opens Service entry creation to pass ports
|
||
.PHONY: test-e2e | ||
test-e2e: compile ## Runs end-to-end tests | ||
$(call header,"Running end-to-end tests") | ||
ginkgo e2e/ -r -v -progress -vet=off -trace --junit-report=ginkgo-test-results.xml ${args} | ||
ginkgo e2e/ -r -progress -vet=off -trace --junit-report=ginkgo-test-results.xml ${args} |
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.
Didn't we add the -v to avoid the circle job to timeout with no output? Don't remember if that was successful or not
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.
That was verbose mode and it resulted in very noisy output. For seeing what's going on -progress
is enough. See latest build https://app.circleci.com/pipelines/github/maistra/istio-workspace/3476/workflows/9bd1b0db-2859-45d0-9cb5-bdc1975663b2/jobs/8767?invite=true#step-108-820
53338bb
to
c5214c6
Compare
/help |
Short description of what this resolves:
Enables working on newly created service through
ike develop new --name new-service -n namespace
which takes care of creating all required k8s resources and then delegates the rest of the work to parentike develop
command. This work supports (and tests) service with outbound-only calls.For the actual test of this new feature see fundamental_use_cases_test.go
Changes proposed in this pull request:
ike develop new
subcommandstring
s to actual files which are then//go:embed
ed for easy on-the-fly manipulationverify
packagePrinter
func to abstract away howruntime.Objects
are printedpkg/
Fixes #1022
TODO
scenario-1.1
for example)Open questions
--name
is not passed should it be autogenerated or is it required?Carry-overs
--swap-deployment
strategy instead