Meraki module feedback re access token

CiscoDevNet / devnet-express-dna-issues

Suggested changes to the content of the learning labs for Devnet Express for DNA

Apache License 2.0

6 stars 2 forks source link

Meraki module feedback re access token #87

Open RuthCattell opened 5 years ago

RuthCattell commented 5 years ago

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 commented 4 years ago

@metahertz can you verify if this has been fixed?

metahertz commented 4 years ago

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

klevenstein commented 4 years ago

Sure was. Paging @denapom11? :)

annegentle commented 4 years ago

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 commented 3 years ago

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?