Skip to content

Deployment.md

Latest commit

 

History

History
102 lines (68 loc) · 3.23 KB

Deployment.md

File metadata and controls

102 lines (68 loc) · 3.23 KB

Run on your own sub

If you want to run this on your own subscription, complete the following tasks:

Deploy the resources

Subscription level deploy all resources

If you want to just do the whole thing at once, just deploy to the subscription.

  1. Make sure you are logged in to your subscription

  2. Make sure you are in the correct subscription in a terminal window

  3. Validate/change any parameters in the allMessagingResources.parmaeters.json file

  4. Run one of the following commands (depending on your shell):

    PowerShell:

    bash deployAll.sh

    or Bash:

    bash ./deployAll.sh

Deploy each resource individually

If you want to deploy each resource individually, you can do so by navigating to the folder of the resource you want to deploy and running the deploy script.

  1. Make sure you are logged in to your subscription

  2. Make sure you are in the correct subscription in a terminal window

  3. Manually create a resource group for the resource you want to deploy in the location of your choice

  4. Validate/change any parameters in the <resource>.parmaeters.json file

  5. Run one of the following commands (depending on your shell):

    PowerShell:

    bash deploy<resource>.sh

    or Bash:

    bash ./deploy<resource>.sh

Create SAS Access Connection Strings

After Deployment, you will need to manually create the SAS connection strings in your event hub and service bus resources.

Event Hub (not the event hub namespace!)

Create access for the SDK using SAS tokens from your event hub.

  1. Open the Event Hub (not the namespace, the hub!)
  2. Click on Shared Access Policies
  3. Click on Add
  4. Add the Producer with Send permissions
  5. Add the Consumer with Listen permissions
  6. Get the values of the connection string for use in the Event Hub Code projects

Service Bus

Create access for the SDK using SAS tokens from your service bus.

  1. Open the Service Bus
  2. Click on Shared Access Policies
  3. Get the RootManageSharedAccessKey connection string for use in the Service Bus Administrator code project

Service Bus Queues

Navigate to the created Queue

  1. Click on Shared Access Policies
  2. Click on Add
  3. Add the Producer with Send permissions
  4. Add the Consumer with Listen permissions
  5. Get the connection strings for use in the code modifications

Service Bus Topics

Navigate to the created Topic

  1. Click on Shared Access Policies
  2. Click on Add
  3. Add the Producer with Send permissions
  4. Add the Consumer with Listen permissions
  5. Get the connection strings for use in the code modifications

Modify Code

After getting all the access tokens created, you will need to modify the code in the projects you want to use

  1. Open the code project in Visual Studio
  2. Modify the secrets.json file with the connection strings you created [use USER SECRETS!]
  3. Leverage the user-secrets-example.txt file to help determine what secrets you need to add to the secrets.json file.

Run the code

After modifying the code, you can run the code in the projects you want to use.