I have a Helm library chart that I can install as a dependency by including it in the same repo and using the filepath, like this:
dependencies:
- name: foo-lib
version: 1.0.0
repository: file://../foo-lib
But once I move the library chart to it's own git repo, every syntax I've tried has been unable to install the chart using helm dependency update. The error says "...is not a valid chart repository or cannot be reached: error converting YAML to JSON: yaml: line 121: mapping values are not allowed in this context", but I don't think it's a yaml conversion issue since I can install the chart with the filepath reference. Is it just completely impossible to do this? If not, what is the syntax?
dependencies:
- name: foo-lib
version: "1.0.0"
repository: "https://github.com/bar/library-charts.git/foo-lib"
Related
I have created a Library chart and uploaded to a GitLab repository. I have also created a package of that library chart and put that in the same repository.
Now, I am creating a application chart and I want to add the library chart as a dependency. But, while doing that I am getting error.
I have tried adding the Gitlab repo as a dependency in application chart.
dependencies:
- name: helm-libraryChart
version: 0.1.6
repository: https://gitlab.com/....../helm-base/-/tree/main
and try "helm dependency build" command.
It's giving error:
Getting updates for unmanaged Helm repositories... update ./plexus-brand-service 1 ✘ ╱ dev ⎈ ╱ 10:08:04 AM
...Unable to get an update from the "https://gitlab.com/...../helm-base/-/tree/main" chart repository:
failed to fetch https://gitlab.com/....../helm-base/-/tree/main/index.yaml : 503 Service Unavailable
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "plexus-helm-repo" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: no cached repository for helm-manager-732a2d2ce82dd5555f40999b4534b023fc381cd8881fe27ac73bceda9e07b27a found. (try 'helm repo update'): open /Users/neeraj.yadav/Library/Caches/helm/repository/helm-manager-732a2d2ce82dd5555f40999b4534b023fc381cd8881fe27ac73bceda9e07b27a-index.yaml: no such file or directory
I upgraded the helm chart from 3.10.8 to 4.2.20 and the Jenkins app from 2.319.2-lts to 2.375.1 (do not change the plugin version in /var/jenkins_home/plugins after the upgrade).
jenkins container having this issue
#reactOnCycle: found cycle in plugin dependencies: (root=Plugin:jackson2-api, deactivating all involved) Plugin:jackson2-api -> Plugin:jersey2-api -> Plugin:jackson2-api
Failed to load: Credentials Plugin (credentials 1214.v1de940103927)
Update required: Configuration as Code Plugin (configuration-as-code 1.55.1) to be updated to 1559.v38a_b_2e3b_6b_b_7 or higher
Update required: Structs Plugin (structs 308.v852b473a2b8c) to be updated to 324.va_f5d6774f3a_d or higher
can you guys guide me how to resolue the jenkins plugin issue
jenkins plugin version not change the presistance volume /var/jenkins_home/plugins
I am currently working on an old flutter project. I want to install the necessary dependencies so that i can start making changes.
Now when i run the flutter pub get command, i get a certain error which is not explaining how to solve it.
pub get failed (server unavailable) -- attempting retry 10 in 64 seconds...
Git error. Command: git clone --mirror git://github.com/tekartik/platform.dart C:\src\flutter2\.pub-cache\git\cache\platform.dart-6f0f0462856ed9b1246d3c594e824b1b2d81f000
stdout:
stderr: Cloning into bare repository 'C:\src\flutter2.pub-cache\git\cache\platform.dart-6f0f0462856ed9b1246d3c594e824b1b2d81f000'...
fatal: unable to connect to github.com:
github.com[0: 140.82.121.3]: errno=Unknown error
I think the point reached for downloading the dependency and it is not showing me where i can change from git:// to git#github
Below is a code snippet of the pubspec.yaml file where the dependency is to be installed
tekartik_app_platform:
git:
url: git#github.com:tekartik/app_flutter_utils.dart.git
ref: null_safety
path: app_platform
version: '>=0.1.0'
I am trying to get help on how to solve it because i only just got the code which is an old code and so am not sure where to go and make the fix.
Thank you alot in advance.
Try changing it to:
git:
url: https://github.com/tekartik/app_flutter_utils.dart
path: app_platform
ref: null_safety
More info on the packages can be found under: Dependencies on unpublished packages
https://docs.flutter.dev/development/packages-and-plugins/using-packages
I managed to find the solution. The ref value the project was using is null safety which still uses "git://" which is not being used by github anymore and so that is where the error is coming from.
So i changed to
tekartik_app_platform:
git:
url: git#github.com:tekartik/app_flutter_utils.dart.git
ref: dart2_3
path: app_platform
version: '>=0.1.0'
If this is the case for adding the plugin dependecy in flutter by git reference
Make sure you have public access for the same repository. if private then go to bottom of general setting and make it public.
I am trying to set constraints for git package dependencies with versions below 1.0.0; however, it might also be versions above, but not sure.
Flutter project depends on two packages that we're hosting on git repositories.
We're referencing them in our pubspec.yaml as git packages
According to the Dart.dev dependencies docs: ^0.1.2 is equivalent to '>=0.1.2 <0.2.0'
However, it's always fetching the latest version on github regardless of our version constraints.
Here is how we are referencing package in our pubspec.yaml like this:
my_private_package:
git:
url: ssh://git#github.com-org/my_private_package/my_private_package.git
ref: develop
version: ^0.30.0
For example: If we have a branch in this repo that's versioned 0.32.1 the code above doesn't seem to work(or rather respect the version constraints) and will simply get 0.32.1 version rather than 0.30.x
Does anyone know how to prevent the flutter pub get command from pulling 0.32.1 in this instance? Is the caret constraint not working because we're pulling from a git repository maybe?
Judging by the documentation on pubspec.yaml dependencies, Git dependencies use the ref key to specify the version to pull from the repository. dart pub and flutter pub don't know how to search through your repository for a package version, so the latest commit on the master branch is chosen by default.
I have following syntax in my requirements.yaml
# umbrella/requirements.yaml
dependencies:
- name: my-chart
version: ~1.0
repository: "#my-repo"
I want to receive all the patches of my-chart every time I run helm dependency update. However, it seems to work only if I have release versions like 1.0.8, 1.0.12, etc. in my-repo. But not for snapshots, e.g. 1.0.13-SNAPSHOT
Error: Can't get a valid version for repositories umbrella
Is that an expected behavior or how should I fix this?