-
Notifications
You must be signed in to change notification settings - Fork 53
SUP-1761 Implement local config pipeline resolver func #234
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
Conversation
jradtilbrook
left a comment
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.
I think looks good, but the order of the resolvers seems wrong. I think we want to use the config file before we try use the API
| resolvers := resolver.NewAggregateResolver( | ||
| resolver.ResolveFromPositionalArgument(args, 1, f.Config), | ||
| resolver.ResolveFromPath("", f.Config.Organization, f.RestAPIClient), | ||
| resolver.ResolveFromConfig(f.LocalConfig), |
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.
I think we want these above the ResolveFromPath
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.
Need to apply this to all the commands
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.
missed to save the other commands and didn't double check the commit 😓
Co-authored-by: Jarryd Tilbrook <jarryd@buildkite.com>
…nto local-config-resolver-fn
This PR implements a pipeline resolver function that searchers for a local config file .bk.yaml. When more than one pipelines are found in the local config, a selection list of pipelines will be prompted to the user
Not implemented in the PR:
Tests