You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to be able to configure root project parameters since some parameters are universal and should not be set on every project. Currently we cannot add parameters to the root project using the provider.
We have found that using a teamcity_project resource and crafting it properly (setting the name and description as they currently exist in TeamCity) allows the root project to be updated after importing the root project state. This doesn't allow users of the provider to use terraform without special steps (importing the root project state) and so should be avoided. We can think of two approaches to implement this feature:
Create a special resource type teamcity_root_project similar to how there is a default_vpc type for AWS which is different from the normal aws_vpc resource type. This would only have the arguments available that can be updated for the root project which is a subset of the arguments for other projects.
2 . Create a resource project_parameters that would allow parameters to be set for any project including the root project. The downside to this is that understanding what the expected outcome should be is difficult when using both a teamcity_project resource and a project_parameters resource. Also if people do not pay attention and look for both resource types they will form an incomplete picture of what should be created.
What would you prefer (including any other options that you can think of).
Please let us know as we aim to implement this feature soon (via the eli-guidewire forks).
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
We need to be able to configure root project parameters since some parameters are universal and should not be set on every project. Currently we cannot add parameters to the root project using the provider.
We have found that using a teamcity_project resource and crafting it properly (setting the name and description as they currently exist in TeamCity) allows the root project to be updated after importing the root project state. This doesn't allow users of the provider to use terraform without special steps (importing the root project state) and so should be avoided. We can think of two approaches to implement this feature:
2 . Create a resource project_parameters that would allow parameters to be set for any project including the root project. The downside to this is that understanding what the expected outcome should be is difficult when using both a teamcity_project resource and a project_parameters resource. Also if people do not pay attention and look for both resource types they will form an incomplete picture of what should be created.
What would you prefer (including any other options that you can think of).
Please let us know as we aim to implement this feature soon (via the eli-guidewire forks).
Thanks
The text was updated successfully, but these errors were encountered: