-
Notifications
You must be signed in to change notification settings - Fork 902
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(rosco): Allow roscoMode per stage/execution #7564
Conversation
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.
LGTM, thanks!
$scope.baseOsOptions.push({ | ||
id: $scope.stage.baseOs, | ||
detailedDescription: 'Custom', | ||
vmTypes: ['hvm', 'pv'], |
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.
oh hey this is kind of a cool idea. only downside is it means we lose the ability to validate OS options that we remove because they're deprecated. but maybe that's ok.
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.
Well the current experience is terrible because it just JSEs.
If we wanted to aggressively validate against deprecated versions, I’d imagine we can return a “deprecated” blacklist or flag from the gate endpoint.
But not sure it’s worth that effort.
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.
yeah, i went through basically the same thought process — i think this is good enough until we decide we need some kind of deprecated indicator
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.
nice!
c2bbf20 feat(rosco): Allow roscoMode per stage/execution (spinnaker#7564) ca176fc feat(provider/aws): Functions (listing and searching) (spinnaker#7568) e49ffaf Revert "feat(provider/aws): Functions (listing and searching) (spinnaker#7536)" (spinnaker#7567) 86a365b feat(provider/aws): Functions (listing and searching) (spinnaker#7536)
* fix(awsbake): Fix exception if an unlisted baseOs is used * feat(bake): Support roscoSelector(stage) to determine roscoMode
c2bbf20 feat(rosco): Allow roscoMode per stage/execution (spinnaker#7564) ca176fc feat(provider/aws): Functions (listing and searching) (spinnaker#7568) e49ffaf Revert "feat(provider/aws): Functions (listing and searching) (spinnaker#7536)" (spinnaker#7567) 86a365b feat(provider/aws): Functions (listing and searching) (spinnaker#7536)
@alanmquach, the Azure provider breaks since Spinnaker version 1.17 and per our tier 1 investigation, this PR might be the root cause. More detail about Azure experience breaking see issue 5104. Could you please help take a look? |
@mybayern1974 I just took a look and it looks like I accidentally duplicated the string |
* fix(awsbake): Fix exception if an unlisted baseOs is used * feat(bake): Support roscoSelector(stage) to determine roscoMode
c2bbf20 feat(rosco): Allow roscoMode per stage/execution (spinnaker#7564) ca176fc feat(provider/aws): Functions (listing and searching) (spinnaker#7568) e49ffaf Revert "feat(provider/aws): Functions (listing and searching) (spinnaker#7536)" (spinnaker#7567) 86a365b feat(provider/aws): Functions (listing and searching) (spinnaker#7536)
This allows deck to be configured to compute
roscoMode
on a per stage/execution basis via an optionalroscoSelector
in settings: