You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We hit an issue when vault resource is used in few pipelines, it's creating a lot of new versions :
concourse=> select count(id) from versioned_resources ;
count
---------
2783265
(1 row)
concourse=> select count(id) from versioned_resources where type='vault';
count
---------
2741569
(1 row)
concourse=> select count(id) from versioned_resources where type!='vault';
count
-------
41699
(1 row)
As you can see, it's populating a bit too much the database and overload it.
I think it should create a new version when vault is really used, not on every check.
Any idea how could we improve this ? Maybe a simple echo [] would be enough as we don't really need to have version/triggering on this part.
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
We hit an issue when vault resource is used in few pipelines, it's creating a lot of new versions :
As you can see, it's populating a bit too much the database and overload it.
I think it should create a new version when vault is really used, not on every check.
Any idea how could we improve this ? Maybe a simple
echo []
would be enough as we don't really need to have version/triggering on this part.Thanks
The text was updated successfully, but these errors were encountered: