-
Notifications
You must be signed in to change notification settings - Fork 32
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
🚀Support for Terraform Cloud Projects #57
Comments
Hi @EmmanuelOgiji, Thank you for your proposal! What do say if the reference to a project will be one of # workspace.yaml
apiVersion: app.terraform.io/v1alpha2
kind: Workspace
spec:
...
project:
name: demo-project
# OR
id: prj-WsVcWRr7SfxRci1v In addition to that, a good question here could be -- what to do if the project doesn't exist? Should we throw an error and exit from the reconciliation or make the workspace a part of the default project? In this case, we can report the project name and ID in the status. It will be either the default one or the one you have configured: status:
project:
name: demo-project
id: prj-WsVcWRr7SfxRci1v Looking forward to hearing your thoughts. Thank you! 👍🏻 |
Hi @arybolovlev , Thanks for the response. I like the idea of the option of either project name or id. I think that is great. For if a project exists or not, I think it depends. If there is going to be a CRD for Projects then I like the idea that if the project does not exist, it just goes to the default one. The user can then correct it if needed later without being blocked (say if it is something critical). Generating an error on the reconcile might be annoying for people. I think this is my preferred option. However, if there is not going to be a Project CRD then maybe the operator can just create a project if it does not exist. |
Thank you! I will try to sum it up in the order it can potentially be implemented.
status:
project:
name: demo-project
id: prj-WsVcWRr7SfxRci1v
apiVersion: app.terraform.io/v1alpha2
kind: Workspace
spec:
...
project:
name: demo-project
# OR
id: prj-WsVcWRr7SfxRci1v As for a new controller to manage projects. I personally like your proposal. And I would really keep it "one-cr-one-project". I cannot tell you when and if that will be implemented due to some other background tasks, however, I would like to ask you to keep posting your proposals or issues/bugs you found. If you feel that there is a question that is not covered in the documentation or FAQ, please let us know. Thank you! 🫶🏻 |
Thank you very much. That sounds good. Projects can be created externally at the moment so that should be fine. Looking forward to seeing the project feature |
This seems like it'd be really useful, thanks for opening an issue on this! |
Hi @EmmanuelOgiji, We are planning to cut a new release with project support this week, please keep an eye on releases. Thanks! |
Description
Given the recent announcement of Terraform Cloud Projects, this should be supported in the workspace CRD.
It would also be worth having a project CRD as well. Otherwise, another option would be to have the operator check if the project in the CRD exists and if not, create it
Potential YAML Configuration
References
Community Note
The text was updated successfully, but these errors were encountered: