Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Required weekday fix #122

Open
wants to merge 27 commits into
base: master
Choose a base branch
from
Open

Conversation

rjh-yext
Copy link

@rjh-yext rjh-yext commented Dec 6, 2022

removing unused variable

cvbarros and others added 27 commits December 18, 2018 23:29
Without this, changes to artifact_paths for an already created resource
with state would result in the 2nd element of diff.GetChange("settings")
to contain only nils. This is possibly a regression of
hashicorp/terraform#17931
This allows the default passthrough importer to work.
Because both build_config_id and the resprective resource IDs are
needed, the importer for those resourrces take both as a space-separated
string in the last argument of `terraform import`.

Read was also updated to remove state for missing artifact dependencies.
…buildconfig

use d.haschange

switch to use forked go-teamcity, add rename support for project and buildconfig
switch to use forked go-teamcity, add rename support for project & buildconfig
TEST=manual
pushed this branch
rebuilt terraform bin with it
tried to use the mode field
Previously VCS entries would only be added but never removed. It now
follows similar behaviour to how steps are updated.
Return error if there are duplicate build step names
Return error if there are duplicate build step names
Also added validation of the cron expression.
This validation occurs during the terraform apply stage.
The goal of this change is to have changes in VCS checkout rules be
detected as a change in the teamcity_build_config resource. This will
detach the VCS root and re-attach it with the new checkout rules.

Prior to this change, updates to checkout rules were not detected, and
the only way to apply them was to manually detach the VCS first.
tested locally on updating the cron_schedule value, trigger_schedule
resource was deleted and recreated instead of showing an error not
able to update
support update to cron_schedule in teamcity_build_trigger_schedule
…y schedule (#14)

For teamcity_build_trigger_schedule resources, if the schedule is weekly, the weekday field must be set
@atavakoliyext atavakoliyext deleted the required_weekday_fix branch August 28, 2024 16:44
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.

6 participants