Steven Collins

the link does work correctly when used with a @see tag and i have tried it in all of these formats as per the docs: ``` {@link namepathOrURL} [link text]{@link...

I can confirm I also had this issue, however after looking through my settings I had my cookies set to "only block cross-site" and once I changed it to "Allow...

:wave: Is planned to be merged at any point? Would very much like to be able to configure this :D

Just as some extra info on this one, I tried crating the volume via a volume specification file with the same information that the nomad_csi_volume resource has and It successfully...

> Hi @CarbonCollins 👋 > > According to the [docs](https://developer.hashicorp.com/nomad/docs/other-specifications/volume#differences-between-create-and-register) volume context should only be set on volume _registration_, that's why it's only present in the `resource_csi_volume_registration` resource. > >...

I dont have any of the previous logs, but I could try generating some new ones with a new volume

Terraform apply log ``` Terraform will perform the following actions: # module.soc_volumes.nomad_csi_volume.tempo_data[0] will be created + resource "nomad_csi_volume" "tempo_data" { + capacity = (known after apply) + capacity_max = "2.0...

Just checked the nomad operator api call and it seems to have populated the context correctly here... I see the "node_attach_driver": "smb"... I have not deployed a job to use...

Just a bit more info at least, I rolled back to 1.8.3 as the check is not present in that release and my deployments now work \o/ but I couldn't...

Sure, this is my templates version of it at least: ```yaml driver: smb-client instance_id: {{ env "NOMAD_ALLOC_ID" }} smb: shareHost: {{ index .Data.data "host" }} shareBasePath: "{{ index .Data.data "share"...