-
Notifications
You must be signed in to change notification settings - Fork 811
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
Oort get server groups #1680
Oort get server groups #1680
Changes from 8 commits
40aba97
eef8445
f18489a
ff6022c
09a4ae7
2e81c24
8a3096c
fd2dcbd
6eaca21
fe2f033
5e78cc1
52fb40e
7d5d94d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -45,7 +45,6 @@ class WaitForNewUpInstancesLaunchTask implements RetryableTask { | |
|
||
// similar check in `AbstractInstancesCheckTask` | ||
def response = oortService.getServerGroup( | ||
stageData.application, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is backwards incompatible as it breaks the API contract with CloudDriver (unless you update CloudDriver, too). In my opinion this should not have been merged as written. Why not try the application specific endpoint after a 404? The app specific endpoint is marked as deprecated (thank you) and can be logged out as such. That would give folks some time to update CloudDriver (perhaps as part of a blessed release). I will probably put up a PR for that if it seems reasonable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You should (ideally) be installing Spinnaker from a list of verified versions. We publish those to avoid having to add all the complexity of supporting multiple endpoints for several releases. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We've been trying to stick with the verified versions, but due to various issues across Spinnaker services we inevitably need to update to newer versions while we keep other services set at the verified version. I agree that ideally we could always stick with the verified versions, but as of yet that has not been the case. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When issues come up can you file them in spinnaker/spinnaker/issues? This way we can help keep Spinnaker as up-to-date as possible by publishing verified cross-component releases. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure. In that same note - how do we prod you guys for a new verified release? Currently 1.4.2 features a number of bugs around Orca pipeline templates and we can't make any progress until we update both Orca and CloudDriver, which we are hesitant to do because we continue to bump into problems (like this one) in our testing environment. The fundamental problem I see with trying to bundle Spinnaker verified releases is that it's treated like a monolithic release, whereas Spinnaker is really a set of microservices. If semver would be taken a bit more seriously, problems like this wouldn't come about (or maybe, come about less) and we could treat Spinnaker like a set of microservices (with confidence) rather than waiting on the "verified release". There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jonsie here's a good overview from @jtk54 about the release process for verified releases if you're interested: https://www.youtube.com/watch?v=aQ1lhi1l18s |
||
stageData.account, | ||
stage.context.region as String, | ||
stage.context.asgName as String | ||
|
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.
Maybe flag the prior function with
@Deprecated
as well hereThere 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.
Good find. Missed that one. Made the change here: https://github.com/spinnaker/orca/pull/1680/files#diff-044981bc49bd67385ca8beec17533501R48
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.
Sweet let's merge