-
Notifications
You must be signed in to change notification settings - Fork 642
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
fix(rosco) Make baked artifacts adhere to the proposed standard #222
fix(rosco) Make baked artifacts adhere to the proposed standard #222
Conversation
@@ -28,4 +28,7 @@ class Artifact { | |||
String version | |||
String reference | |||
Map<String, String> metadata | |||
String auth |
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.
This should be using the kork-artifacts package instead of recreating this here
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.
Cool, I hadn't seen the kork-artifacts
. Fixing
Artifact bakedArtifact = new Artifact( | ||
name: bakeRecipe?.name, | ||
version: bakeRecipe?.version, | ||
type: cloudProvider, | ||
type: "${cloudProvider}/image/${region}", |
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.
We're relying on the location
field in the artifact definition for region
6ae5baf
to
93e070a
Compare
Now using the |
93e070a
to
ccc6e94
Compare
@lwander anything else we need to merge this? |
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.
This should make the artifacts created in Rosco follow the same standard as those created in Orca (spinnaker/orca#1441)