-
Notifications
You must be signed in to change notification settings - Fork 100
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
add context argument to resource.nomad_csi_volume #503
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7533140
to
5c36efa
Compare
This was referenced Jan 16, 2025
cc795db
to
c4e0492
Compare
|
The `context` output is missing from `resource.nomad_csi_volume`. This prevents successfully migrating from the deprecated `resource.nomad_external_volume`. Fixes: #494 Ref: https://hashicorp.atlassian.net/browse/NET-11851
c4e0492
to
7629241
Compare
pkazmierczak
approved these changes
Jan 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
tgross
added a commit
to hashicorp/nomad
that referenced
this pull request
Jan 23, 2025
When a volume is updated, we merge the new definition to the old. But the volume's context comes from the plugin and is likely not present in the user's volume specification. Which means that if the user re-submits the volume specification to make an adjustment to the volume, we wipe out the context field which might be required for subsequent operations by the CSI plugin. This was discovered to be a problem with the Terraform provider and fixed there, but it's also a problem for users of the `volume create` and `volume register` commands. Update the merge so that we only overwrite the value of the context if it's been explictly set by the user. We still need to support user-driven updates to context for the `volume register` workflow. Ref: hashicorp/terraform-provider-nomad#503 Fixes: democratic-csi/democratic-csi#438
6 tasks
tgross
added a commit
to hashicorp/nomad
that referenced
this pull request
Jan 23, 2025
When a volume is updated, we merge the new definition to the old. But the volume's context comes from the plugin and is likely not present in the user's volume specification. Which means that if the user re-submits the volume specification to make an adjustment to the volume, we wipe out the context field which might be required for subsequent operations by the CSI plugin. This was discovered to be a problem with the Terraform provider and fixed there, but it's also a problem for users of the `volume create` and `volume register` commands. Update the merge so that we only overwrite the value of the context if it's been explictly set by the user. We still need to support user-driven updates to context for the `volume register` workflow. Ref: hashicorp/terraform-provider-nomad#503 Fixes: democratic-csi/democratic-csi#438
tgross
added a commit
to hashicorp/nomad
that referenced
this pull request
Jan 23, 2025
When a volume is updated, we merge the new definition to the old. But the volume's context comes from the plugin and is likely not present in the user's volume specification. Which means that if the user re-submits the volume specification to make an adjustment to the volume, we wipe out the context field which might be required for subsequent operations by the CSI plugin. This was discovered to be a problem with the Terraform provider and fixed there, but it's also a problem for users of the `volume create` and `volume register` commands. Update the merge so that we only overwrite the value of the context if it's been explictly set by the user. We still need to support user-driven updates to context for the `volume register` workflow. Ref: hashicorp/terraform-provider-nomad#503 Fixes: democratic-csi/democratic-csi#438
6 tasks
tgross
added a commit
to hashicorp/nomad
that referenced
this pull request
Jan 23, 2025
When a volume is updated, we merge the new definition to the old. But the volume's context comes from the plugin and is likely not present in the user's volume specification. Which means that if the user re-submits the volume specification to make an adjustment to the volume, we wipe out the context field which might be required for subsequent operations by the CSI plugin. This was discovered to be a problem with the Terraform provider and fixed there, but it's also a problem for users of the `volume create` and `volume register` commands. Update the merge so that we only overwrite the value of the context if it's been explictly set by the user. We still need to support user-driven updates to context for the `volume register` workflow. Ref: hashicorp/terraform-provider-nomad#503 Fixes: democratic-csi/democratic-csi#438
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
context
output is missing fromresource.nomad_csi_volume
. This prevents successfully migrating from the deprecatedresource.nomad_external_volume
. Add it as a computed value that we get from the plugins.Fixes: #494
Fixes: #417
Ref: https://hashicorp.atlassian.net/browse/NET-11851
Tested using the most recent available Docker release of democratic-csi (v1.9.3, not sure why the version shows as 1.9.0 below).
terraform configuration
terraform apply
terraform plan to verify no changes
Results from Nomad API: