Closed mariiahnied closed 3 years ago
Week 3 Step 8 ⬤⬤⬤⬤⬤⬤⬤⬤◯ | 🕐 Estimated completion: 10-20 minutes
Modify the deepsecrets
Azure Function to
deepsecrets/index.js
to the deepsecrets
branch❗ Make sure to return your message in this format:
Thanks 😊! Stored your secret "insert_user's_message". 😯 Someone confessed that: "a_random_secret"
To test your work, send your Twilio number a text message. You should still receive a text back that contains a message similar to the one below, but now the second secret returned will be random, and no longer the most recent secret stored!
Thanks 😊! Stored your secret "insert_user's_message". 😯 Someone confessed that: "a_random_secret"
💡 Yay! This means you've successfully queried for and returned a random secret.
In your createDocument
function, you'll first want to modify the original SQL query to now query for all secrets inside your container.
Next, you'll want to select a random secret by:
Math.floor()
and Math.random()
):bulb: Make sure to change your responseMessage to return the correct index of items
.
Please complete after you've viewed the Week 3 livestream! If you haven't yet watched it but want to move on, just close this issue and come back to it later.
Help us improve BitCamp Serverless - thank you for your feedback! Here are some questions you may want to answer:
I enjoyed the new format, however I also liked the previous as well since I was able to ask questions on livestreams. I had an issue with step 5, so it took me two days to play around with code, so the bot finally accepted it. I liked how the instructions for CosmoDB were linked to the actual documentation instead of just provided here, it gave some insights in how too read a documentation.
What was confusing about this week? If you could change or add something to this week, what would you do? Your feedback is valued and appreciated!
Jpeg and jpg extensions were confusing. However, the rest was pretty clear. Thanks!
Go ahead and merge this branch to main
to move on. Great work finishing this section!
⚠️ If you receive a
Conflicts
error, simply pressResolve conflicts
and you should be good to merge!
Changes made
Closes #[issue number]