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
Describe the bug
A clear and concise description of what the bug is.
Split from issue #740 as this issue requires an unrelated fix.
The provider cannot find project triggers when attempting to import. It fails with the error
Octopus API error: Resource is not found or it doesn't exist in the current space context. Please contact your administrator for more information. []
When running terraform import, the space ID of the resource is undefined within the resourceProjectScheduledTriggerRead method. We currently use the space ID from the provider as a fallback.
Expected behavior
A clear and concise description of what you expected to happen.
The provider succeeds in discovering the scheduled project trigger
Logs and other supporting information
Add the output of running tf plan or tf apply along with any errors in the Octopus Server logs.
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Octopus API error: Resource is not found or it doesn't exist in the current space context. Please contact your administrator for more information. []
│
│ with octopusdeploy_project_scheduled_trigger.sandbox_cleanup_report,
│ on projects_administration.tf line 108, in resource "octopusdeploy_project_scheduled_trigger" "sandbox_cleanup_report":
│ 108: resource "octopusdeploy_project_scheduled_trigger" "sandbox_cleanup_report" {
│
╵
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Environment and versions:
OS: Linux, OSX
Octopus Server Version: 2024.3.10026
Terraform Version: 1.8.2
Octopus Terraform Provider Version: 0.18.1
Additional context
Add any other context about the problem here.
Note copied from issue #740 : It doesn't appear newer versions of the provider have touched this resource but I have not upgraded as the migration to tenant_project resources is a breaking change which is going to require a fair amount of work
The text was updated successfully, but these errors were encountered:
We should be able to resolve this issue by handling imports in a similar way to how they are handled for environments. This requires us to migrate this resource to use terraform-plugin-framework
Describe the bug
A clear and concise description of what the bug is.
Split from issue #740 as this issue requires an unrelated fix.
The provider cannot find project triggers when attempting to import. It fails with the error
When running
terraform import
, the space ID of the resource is undefined within theresourceProjectScheduledTriggerRead
method. We currently use the space ID from the provider as a fallback.Steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
The provider succeeds in discovering the scheduled project trigger
Logs and other supporting information
Add the output of running
tf plan
ortf apply
along with any errors in the Octopus Server logs.Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Environment and versions:
Linux
,OSX
2024.3.10026
1.8.2
0.18.1
Additional context
Add any other context about the problem here.
Note copied from issue #740 : It doesn't appear newer versions of the provider have touched this resource but I have not upgraded as the migration to
tenant_project
resources is a breaking change which is going to require a fair amount of workThe text was updated successfully, but these errors were encountered: