-
Notifications
You must be signed in to change notification settings - Fork 900
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(gce): Support new artifact model for deploy SG #7178
Conversation
refactored the deploy SG to use the new artifacts rewrite and added the support for custom artifacts. corresponding PRS: prewrite: |
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 so much Jammy! Just to make sure I understand since I've actually never used artifacts in a GCE deploy workflow: the GCE image artifacts are currently represented as "custom" kinds, which are deprecated post-rewrite, so you added the CUSTOM_OBJECT kind in the PR to maintain backwards compatibility?
yes that is correct. According to the comments in the code it only used the custom artifact type. I have some suspicions it hasn't worked for awhile without the changes I made |
ecb2dd1 feat(gce): Support new artifact model for deploy SG (spinnaker#7178) c93b4d0 fix(executions): Clarify why executions are NOT_STARTED (spinnaker#7183) 1f3882b fix(core/pipeline): Change 'pipelines' state to redirect to the default child 'executions' ... instead of having an abstract state
ad483a0 fix(google): replace stateful MIG image input with dropdown (spinnaker#7210) 97db30b perf(google): improve performance of GCE image selection (spinnaker#7208) f340b02 feat(google): support stateful MIG operations (spinnaker#7196) ecb2dd1 feat(gce): Support new artifact model for deploy SG (spinnaker#7178)
No description provided.