can rebar3 accepts deps in tar.gz or zip format

[phani35]

Is it possible to provide deps in tar.gz or zip format in rebar.config?

[tsloughter]

I assume you mean a local file? No. A custom dependency resource module would be required to support dependencies like that.

Maybe "checkout dependencies" fits your use case, https://www.rebar3.org/docs/configuration/dependencies/#checkout-dependencies

[phani35]

it may be local or downloaded from external storages like jfrog or nexus or s3.

%% Source Dependencies
{rebar, {https, "https://github.com/erlang/archive/rebar3.tar.gz"}},

Thanks,
Phani

[ferd]

No, these dependencies aren't supported. Adding these would require a custom dependency handler: https://rebar3.org/docs/extending/custom_dep_resources/

Such handler needs to implement the following API:

%% Type declarations
-type resource() :: #resource{}. % an opaque record generated by an API call described below
-type source() :: {type(), location(), ref()} | {type(), location(), ref(), binary()}.
-type type() :: atom().
-type location() :: string().
-type ref() :: any().
-type resource_state() :: term().

%% and the following callbacks
-callback init(type(), rebar_state:t()) -> {ok, resource()}.
-callback lock(rebar_app_info:t(), resource_state()) -> source().
-callback download(file:filename_all(), rebar_app_info:t(), rebar_state:t(), resource_state()) ->
    ok | {error, any()}.
-callback needs_update(rebar_app_info:t(), resource_state()) -> boolean().
-callback make_vsn(rebar_app_info:t(), resource_state()) ->
    {plain, string()} | {error, string()}.

These require you to be able to create a lock file definition from the fetched resource (eg. a hash value representing the tarball signature), to download the file (call the endpoint via HTTP(s) and do the appropriate validation and error reporting), be able to define whether the library that was downloaded no longer fits the version specified in rebar.config (or the lock file), and then generate a version name for the library at that location (or that was downloaded).

Since there isn't a generic way to make this work with a tarball, you're likely going to choose a few extra mechanisms to handle the metadata, or willingly write a plugin that ignores these requirements and risks breaking other functionality of Rebar3 (like properly updating deps on disk when switching your repo's git branches that require a different version).