Justin Keller

What's going on? Just today started getting: ``` Error: can't get a valid version for repositories postgresql. Try changing the version constraint in Chart.yaml ``` Chart.yaml is: ``` - name:...

Also, the suggested link with all versions is returning 404 as well: https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami Any recommendations? Need to get this resolved, breaking all of our deployments.

@thomasv314 thanks. I tried the following: ```shell $ helm repo remove bitnami "bitnami" has been removed from your repositories $ helm repo add bitnami https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami/ "bitnami" has been added to...

Now, breaking on RabbitMQ, even with using `helm repo add bitnami https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami/`. The `Chart.yaml` for our RabbitMQ is: ``` annotations: category: Infrastructure apiVersion: v2 appVersion: 3.9.8 dependencies: - name: common...

@carrodher any idea why RabbitMQ is still broken even when using `bitnami https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami/`? ``` - name: rabbitmq version: 8.24.1 repository: https://charts.bitnami.com/bitnami ```

> Keep the old index.yaml, deprecate that location (no longer give it updates), and put newer charts on a different URL with different guarantees about longevity Yes 💯 .

Sure, so I have two models: ``` // Domain.js 'use strict'; const orm = require('../lib/orm.js'); const type = orm.type; const config = require('../lib/config.js'); const Domain = module.exports = orm.createModel(orm.getTableName(__filename), {...

After creating an `id` field in `Domain.js` and switching the primary key to `id` from `domain`, this problem went away. However, it still might be a bug/issue.

👍

This would be super useful for fields like id, created, updated, anything that is computed automatically.