Skip to content

Default behaviour for auto_inactive doesn't work as expected #92

@NickGraham101

Description

@NickGraham101

After upgrading from v0.6.2 to v1 we encountered a rate limiting issue with the default settings of, I've discussed this further here.

We attempted to resolve this by changing override to false and relying on the default setting of true for auto_inactive however this was only partially successful. We no longer get rate limited because there are no API calls being made to update the inactive deployments. However the status of the previous deployments are not getting updated, I believe this is because all deployments are now created with transient_environment: true.

As per the docs:

When you set the state of a deployment to success, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become inactive.

I created a simple pipeline here which shows the multiple active deployments here.

Is it possible to make transient_environment a configurable value again?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions