Cosmos StoredProcedure

using System;
using System.Net.Http;
using System.Threading.Tasks;

namespace CosmosCreateSproc
{
    class Program
    {
        static async Task Main(string[] args)
        {
            HttpClient client = new HttpClient();

            string key = "*******************..........";
            string dte = DateTime.UtcNow.ToString("R");
            string cosmos_acct = "cosmos-***********";
            string cosmos_db = "ToDoList";
            string cosmos_container = $"Items";
            string procName = "TESTSPROC_DELETE";

            string procDef = "function() {\r\n var context = getContext();\r\nvar response = context.getResponse();\r\nresponse.setBody(%22Hello, World%22);\r\n}";

            client.BaseAddress = new Uri($"https://{cosmos_acct}.documents.azure.com");
            client.DefaultRequestHeaders.Add("x-ms-version", "2018-12-31");
            client.DefaultRequestHeaders.Add("Accept", "application/json");
            client.DefaultRequestHeaders.Add("x-ms-date", dte);

            string authTkn = GenerateAuthToken("POST", "sprocs", $"dbs/{cosmos_db}/colls/{cosmos_container}", dte, key, "master", "1.0");
            await CreateSproc(client, authTkn, procName, procDef, cosmos_db, cosmos_container);

            client.Dispose();

            Console.ReadKey();
        }

        static async Task CreateSproc(HttpClient client, string auth, string sprocname, string sprocDef, string database, string container)
        {
            string payload = $"{{ \"body\": \"{sprocDef}\", \"id\": \"{sprocname}\" }}";

            using (var msg = new HttpRequestMessage(HttpMethod.Post, $"dbs/{database}/colls/{container}/sprocs"))
            {
                StringContent sc = new StringContent(payload);
                msg.Content = sc;
                msg.Headers.Add("authorization", auth);
                using (var response = await client.SendAsync(msg))
                {
                    string responseMsg = await response.Content.ReadAsStringAsync();
                    Console.WriteLine(responseMsg);
                    response.EnsureSuccessStatusCode();
                }
            }
        }

        // Creates an Auth token for Cosmos REST API per spec.
        static string GenerateAuthToken(string verb, string resourceType, string resourceId, string date, string key, string keyType, string tokenVersion)
        {
            var hmacSha256 = new System.Security.Cryptography.HMACSHA256 { Key = Convert.FromBase64String(key) };

            verb = verb ?? "";
            resourceType = resourceType ?? "";
            resourceId = resourceId ?? "";

            string payLoad = string.Format(System.Globalization.CultureInfo.InvariantCulture, "{0}\n{1}\n{2}\n{3}\n{4}\n",
                    verb.ToLowerInvariant(),
                    resourceType.ToLowerInvariant(),
                    resourceId,
                    date.ToLowerInvariant(),
                    ""
            );

            byte[] hashPayLoad = hmacSha256.ComputeHash(System.Text.Encoding.UTF8.GetBytes(payLoad));

            string signature = Convert.ToBase64String(hashPayLoad);

            return System.Net.WebUtility.UrlEncode(String.Format(System.Globalization.CultureInfo.InvariantCulture, "type={0}&ver={1}&sig={2}",
                keyType,
                tokenVersion,
                signature));
        }
    }
}

I decided to install the Cosmos extension for VS Code and see what happened. I get "Error: Unexpected Token":

Hi Bob, Can you detail the entire key you are using minus 10 characters in the middle to keep the key private. I am looking primarily for the first few characters and the last few characters but want preserve the exact character count. Additionally, is this the primary key or a read-only key taken from the "keys" blade in the portal? I am trying to figure out if there is something about the specific token that is being passed, and is being replicated each time you attempt this in a different subscription? Thank you, Mike

The product group responded and confirmed this is a product issue:

Thanks for your feedback. Right now, creating SP via REST api will accept unescaped js code. However, when portal read on stored procedures, it will run into invalid JSON issue. Our backend is working on a fix for this, but no timeline is known at this point.
I encourage you to create sp from portal, which will make sure you have valid sp for portal to consume.

Thank you!

Very good, thank you for all your help.

…

On Mon, Oct 21, 2019 at 6:10 PM Mike Ubezzi ***@***.***> wrote: The product group responded and confirmed this is a product issue: Thanks for your feedback. Right now, creating SP via REST api will accept unescaped js code. However, when portal read on stored procedures, it will run into invalid JSON issue. Our backend is working on a fix for this, but no timeline is known at this point. I encourage you to create sp from portal, which will make sure you have valid sp for portal to consume. Thank you! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://gist.github.com/4db3151b3d0297816b2dbfb778982bd9?email_source=notifications&email_token=ABAD7QFNKCCXHF6ZUVKQLH3QPYSFJA5CNFSM4JCBMQ7KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAF24CI#gistcomment-3061796>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAD7QHQEEAH76T5XE54LVTQPYSFJANCNFSM4JCBMQ7A> .

-- Bob Crowley w <http://www.crowcoder.com/>ww.contrivedexample.com

Very good, thank you for all your help.