Repository navigation
allow allow contribute a search filter in jira bridge #505
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
Changes from all commits
69dd0f2
5da77b1
f3da9fb
d2bcafb
9213a4e
9dfef20
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 |
|---|---|---|
|
|
@@ -36,11 +36,11 @@ type BridgeImpl interface { | |
| } | ||
|
|
||
| type Importer interface { | ||
| Init(ctx context.Context, repo *cache.RepoCache, conf Configuration) error | ||
| Init(ctx context.Context, repo *cache.RepoCache, name string, conf Configuration) error | ||
|
Contributor
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. I don't understand why you would need to pass the bridge name. This name is purely arbitrary for the user to identify configured bridges, so it's not valuable for anything else. Am I missing something?
Author
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. For replacing the project id, will be used for the export filtering in the bridge. I missed that change, will update the pull request with.
Author
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. I was thinking about sharing the bridges configuration in the repository itself. All the contributors are using the same no ? This way when a contributor clone the repository, he'll get the associated bridges with. He will only have to give his credentials. |
||
| ImportAll(ctx context.Context, repo *cache.RepoCache, since time.Time) (<-chan ImportResult, error) | ||
| } | ||
|
|
||
| type Exporter interface { | ||
| Init(ctx context.Context, repo *cache.RepoCache, conf Configuration) error | ||
| Init(ctx context.Context, repo *cache.RepoCache, name string, conf Configuration) error | ||
| ExportAll(ctx context.Context, repo *cache.RepoCache, since time.Time) (<-chan ExportResult, error) | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,13 +19,14 @@ const ( | |
| metaKeyJiraDerivedId = "jira-derived-id" | ||
| metaKeyJiraKey = "jira-key" | ||
| metaKeyJiraUser = "jira-user" | ||
| metaKeyJiraProject = "jira-project" | ||
| metaKeyJiraBridge = "jira-bridge" | ||
|
Contributor
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 a breaking change, it's going to break the import of people already using that bridge.
Author
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. not sure, I've planned to use the bridge as the selector. ie: the bridge that import should do the export. I think it's a more strict this way. This is because I'm replacing the project constraint with the filter if defined.
Author
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 can have a back-ward mechanism, will preserve the project meta key and use it if there is no jira bridge key defined. The jira bridge meta key will be only used when the user will have provided a filter overriding the project filter. |
||
| metaKeyJiraBaseUrl = "jira-base-url" | ||
| metaKeyJiraExportTime = "jira-export-time" | ||
| metaKeyJiraLogin = "jira-login" | ||
|
|
||
| confKeyBaseUrl = "base-url" | ||
| confKeyProject = "project" | ||
| confKeyFilter = "filter" | ||
| confKeyDefaultLogin = "default-login" | ||
| confKeyCredentialType = "credentials-type" // "SESSION" or "TOKEN" | ||
| confKeyIDMap = "bug-id-map" | ||
|
|
||
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.
why would you need to read the global config? The bridge config only make sense and is stored locally.
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.
For sharing bridges definition in multiple projects. This way I can define them only once for the multiple repositories we're working on in the same jira project.