Skip to content

Database filled by versionned_resources entries #10

Description

@Seraf

Hello,

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions