Skip to content

fix: determine credential generation status from the task expiry - #167

Merged
Agrendalath merged 1 commit into
mainfrom
agrendalath/fix-credential-configuration-generation-status
Oct 19, 2026
Merged

Agrendalath merged 1 commit into
mainfrom
agrendalath/fix-credential-configuration-generation-status

Conversation

@Agrendalath

Copy link
Copy Markdown
Member

Celery Beat maintains the enabled flag of a periodic task itself - it disables expired tasks and one-off tasks that have already run - so the flag does not reliably reflect the intended configuration.

This adds a CredentialConfiguration.is_generation_enabled property that uses the expires field of the periodic task when it is set, and falls back to the enabled flag otherwise. The credential eligibility endpoint now reports this value.

Celery Beat maintains the `enabled` flag of a periodic task itself - it
disables expired tasks and one-off tasks that have already run - so the
flag does not reliably reflect the intended configuration.

Add a `CredentialConfiguration.is_generation_enabled` property that uses
the `expires` field of the periodic task when it is set, and falls back
to the `enabled` flag otherwise. The credential eligibility endpoint now
reports this value.
@Agrendalath
Agrendalath force-pushed the agrendalath/fix-credential-configuration-generation-status branch from 7e72186 to 21fca1e Compare October 19, 2026 23:17
@Agrendalath Agrendalath self-assigned this Oct 19, 2026
@Agrendalath
Agrendalath merged commit 13b1277 into main Oct 19, 2026
13 checks passed
@Agrendalath
Agrendalath deleted the agrendalath/fix-credential-configuration-generation-status branch October 19, 2026 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant