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
Add triggers support to spiceai_deployment resource
- Add triggers argument to spiceai_deployment to force new deployments
- Document triggers usage in resource schema and examples
- Warn users on delete that deployments are not stopped
- Add mapPlanModifierRequiresReplace for triggers attribute
- Add spicepod normalization and plan modifier tests
A deployment uses the app's current spicepod configuration and deploys it to the Spice.ai cloud infrastructure. Deployments are immutable - any changes to deployment parameters will create a new deployment.
68
69
70
+
~> **Note:** Deployments are append-only log entries. Removing this resource from your configuration will only remove it from Terraform state - it will NOT stop or affect the running instance. To deploy new changes, modify the configuration or triggers to create a new deployment.
MarkdownDescription: "A map of arbitrary strings that, when changed, will force a new deployment to be created. Use this to trigger deployments based on external changes, such as spicepod configuration updates. Similar to `triggers` in `null_resource`.",
126
+
Optional: true,
127
+
ElementType: types.StringType,
128
+
PlanModifiers: []planmodifier.Map{
129
+
mapPlanModifierRequiresReplace{},
130
+
},
131
+
},
102
132
"image_tag": schema.StringAttribute{
103
133
MarkdownDescription: "Override the Spice.ai runtime image tag for this deployment. If not specified, uses the app's configured image tag. Changing this forces a new deployment to be created.",
0 commit comments