Support special prefixes in aqua.yaml's package name fields to specify Renovate datasources #2018
Unanswered
suzuki-shunsuke
asked this question in
Feature Request
Replies: 2 comments 2 replies
-
Hmm. To avoid the conflict of package names, package names should have the namespace. The package name |
Beta Was this translation helpful? Give feedback.
2 replies
-
- name: crate.io/skim@0.10.4
- name: gitea.com/gitea/tea@v0.9.2
- name: gitlab.com/gitlab-org/cli@v1.29.4 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Feature Overview
Support special prefixes in aqua.yaml's package name fields to specify Renovate datasources.
Why is the feature needed?
Basically, aqua-renovate-config updates packages using github-releases datasource.
Sometimes we want to use other datasources such as
go
andcargo
, but there is no consistent way to do it.So it is good to define the consistent way to specify Renovate datasource.
Basically, Renovate datasource is needed for aqua.yaml and isn't needed for registry.yaml.
As for registry.yaml, aqua supports version_source field, so we will be able to support other datasources for
aqua g
.Does the feature include Breaking Changes?
Basically no.
Note that if we specify the prefix in existing packages, old aqua can't install them.
e.g.
Example Code
aqua.yaml
e.g.
Other approach 1. Support special code comment
e.g.
The concern of this approach is
aqua g
has to generate code comment. It may be difficult.Reference
Beta Was this translation helpful? Give feedback.
All reactions