-
Notifications
You must be signed in to change notification settings - Fork 44
feat: added support for pinning service configs #104
Changes from 1 commit
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 |
---|---|---|
@@ -0,0 +1,13 @@ | ||
package config | ||
|
||
// Pinning configures the pinning services. | ||
type Pinning struct { | ||
// Services lists the pinning services | ||
Services []PinningServices | ||
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. @aschmahmann @jacobheun Q: How are we going to store automated policy per Pinning service? IIUC we will have the default which is manual ( Do we need to add an array 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. @aschmahmann @petar
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. Yep, I think there should be an array of policies per service. I think @petar wasn't sure if we wanted Pinning.RemoteServices to be an array or a map indexed by the service name.
aschmahmann marked this conversation as resolved.
Show resolved
Hide resolved
|
||
} | ||
|
||
type PinningServices struct { | ||
aschmahmann marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Name string | ||
ApiEndpoint string | ||
ApiKey string | ||
lidel marked this conversation as resolved.
Show resolved
Hide resolved
|
||
} |
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.
previously missed
go fmt