teamcity_build_config - Build Step Ordering

[MattHodge]

There is currently no way to control the build step ordering inside the teamcity_build_config resource.

Given the following Terraform:

resource "teamcity_project" "step_ordering" {
  name = "Build Step Ordering"
}

resource "teamcity_build_config" "step_ordering" {
	name = "build config test"
	project_id = "${teamcity_project.step_ordering.id}"

	step {
		type = "cmd_line"
		name = "01 - First"
		code = "echo \"Hello First\""
	}

	step {
		type = "cmd_line"
		name = "02 - Second"
		code = "echo \"Hello Second\""
	}

	step {
		type = "cmd_line"
		name = "03 - Third"
		code = "echo \"Hello Third\""
	}
}

The steps are created in a different order:

[ss-remygreinhofer]

Would "simply" changing the schema to having a list of steps be right way to solve this issue?

[cvbarros]

This has been fixed locally, I'm delaying the push because it will be a breaking change for existing state, so I'm thinking how the best approach would be - to either start creating state migrations or just a hard compatibility break (which would adhere to current SemVer under 1.x).

[lmayorga1980]

This is a very nice to have. Currently I have different results during changes on the steps.

[augustgerro]

Any ideas on how to work around for now?

Let's say, I have three steps with:

1. build a docker container
2. push it
3. deploy it

When steps go not one after one it's broke all builds.

[cvbarros]

Fixed via #70