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?
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 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"
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.
Running into this module error no one on my team, which is all new, does not know. Below is my terraform version. And yes, I know terraform 0.11 is old as hell but I was just hired and have to fix this.
$ terraform --version
Terraform v0.11.14
provider.aws v2.70.0
provider.grafana v1.10.0
provider.kubernetes v1.8.0
provider.null v2.1.2
provider.postgresql v1.7.2
provider.random v2.3.1
Error:
Error: Error asking for user input: 1 error occurred:
* module.editedout-dev-keycloak.provider.grafana: Incompatible API version with plugin. Plugin version: 5, Core version: 4
As described in the documented requirements for the Grafana provider version 1.10, the minimum core version of Terraform for that version of the provider is 0.12. The reason for this can be seen referenced in the CHANGELOG with issue 159. The provider upgraded to version 2 of the provider SDK, which enforces core Terraform at minimum version 0.12. More details around that minimum version bump can be read in that issue description.
If you want to move forward, then you would need to lock in the Grafana provider to version 1.9.0. In Terraform version 0.11, you would achieve that with the following declarative syntax in a config file for the root module config, or preferably in the module declared as editedout-dev-keycloak in the error message you displayed:
provider "grafana" {
version = "1.9.0"
}