-
Notifications
You must be signed in to change notification settings - Fork 175
Add functions for downloading artifacts from nexus #150
base: main
Are you sure you want to change the base?
Conversation
Where do we set the type of binary storage from the point of view of the pipeline itself? |
So your params would look something like this:
And params in the pipeline would be declared as:
|
But the params are env vars. Where do you pass the env var to a concrete function? Maybe you should change the function parameter to retrieve the value from an env var? |
I had another look at it (finally) and it looks great but I think we can try sth better (we'll see if it is better indeed). IMO the function params should be used only if sth can change at runtime (e.g. group id, artifact id). The binary storage type - nexus / artifactory is sth that we can set at the beginning as an env variable. That way we won't have to pass them as function parameters, which means that we're not breaking the compatibility and we're hiding such information that there are different types of binary storages. How about we pass it as an environment variable and reason about this inside BTW I really liked the |
That's fair. I didn't see the pattern for function parameters being intended for runtime only variables which makes a lot of sense. I like you're idea of reasoning about the repository inside the |
Ping @malston ;) |
PR covers using the current beta version of the API for Nexus (v3) and the legacy api for Nexus. Still need to create docker images and run through the example pipelines using both versions of Nexus.