[Bug] - Duplicate Pipeline schedules

[RajasGujarathi]

Describe the bug

We have a GitLab project, and the pipeline of this project needs to run once a day in order to achieve a defined task. In order to achieve daily runs we are using Scheduled pipelines (Gitlabform Pipeline schedules).

With the following configuration, every time the pipeline runs, it creates a new schedule every 2nd time

some-project:

    # Periodic execution Schedule
    schedules:
        "Daily":
            description: "Execute Pipeline daily, to avoid configuration divergence"
             ref: main
             cron: 0 3 * * * # Daily at 3:00 AM
             active: true

Observation,

First Run: Schedule created with Description Daily
Second Run: Schedule updated with Description Execute Pipeline daily, to avoid configuration divergence
Total Schedules: 1

Third Run: Schedule created with Description Daily
Fourth Run: Schedule updated with Description Execute Pipeline daily, to avoid configuration divergence
Total Schedules: 2

Working Fix

Schedules works as expected after changing the configuration to (description attribute has been removed) :

some-project:

    # Periodic execution Schedule
    schedules:
        "Daily":
             ref: main
             cron: 0 3 * * * # Daily at 3:00 AM
             active: true

GitLabForm version
🏗 GitLabForm version: 3.5.0 = the latest stable 😊

GitLab version
GitLab Enterprise Edition 15.8.0-ee

Credits:
Working fix provided by (Removing description attribute) - Aver Mimas (@amimas)

[gdubicki]

Hey @RajasGujarathi!

The docs were already saying that you should put the schedule's description as the key here:

projects_and_groups:
  group_1/project_1:
    schedules:
      "Some schedule": # <--- description
        ref: main
        cron: "0 * * * MON-FRI"
        cron_timezone: "London"
        active: false

...so I wouldn't really call the app behaviour a bug.

We also have merged you PR with docs clarification. Thanks again for the contribution! :)

That's why I think that we can now just close this issue.

[RajasGujarathi]

Yes I agree @gdubicki 😊|