Meraki module feedback re access token

[RuthCattell]

IFeedback from a recent event: in the env_user.py file you need to change it from WT_ACCESS_TOKEN to SPARK_ACCESS_TOKEN

[klevenstein]

@metahertz can you verify if this has been fixed?

[metahertz]

@klevenstein Think you may be looking for another DA :)

[klevenstein]

Sure was. Paging @denapom11? :)

[annegentle]

I think what can happen is that when someone runs a DNA DNE, that code still uses SPARK_ACCESS_TOKEN, so if they also choose to put Meraki into their DNA curriculum, this conflict will occur. @RuthCattell Are SEs still allowed to include Meraki in the DNA DNE?

[klevenstein]

I'm guessing this refers to the SPARK_ACCESS_TOKEN line in
https://github.com/CiscoDevNet/dne-dna-code/blob/master/env_user.template

It sounds like this may not be an issue if Meraki isn't part of the DNA DNE anymore? Or does this issue come up in Meraki DNEs? @annegentle thoughts on who can clarify this?