Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Github branch name in Deploy to Azure is incorrect #23

Open
SeaDude opened this issue Sep 17, 2022 · 0 comments
Open

Default Github branch name in Deploy to Azure is incorrect #23

SeaDude opened this issue Sep 17, 2022 · 0 comments

Comments

@SeaDude
Copy link

SeaDude commented Sep 17, 2022

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  1. Create a new Resource Group
  2. Create a new Azure Communication Service (ACS)
  3. Get a toll-free phone number for the ACS
  4. Create an App Service Plan to host the Azure Event Grid Viewer (AEGV)
    • Requires Windows OS
    • Select West US 2 region
    • Select F1 SKU
    • image
  5. Click the Deploy to Azure button for the Azure Event Grid Viewer (AEGV)
  6. Launch the AEGV web app to ensure its working
    • image
  7. Create an Event Grid Subscription (EGSUB) for the ACS
    • On the ACS blade, click Events
    • + Event Subscription
    • Name: eg-sub-<project>-eg-viewer
    • Event Schema: Event Grid Schema
    • System Topic Name: eg-sys-topic-<project>-eg-viewer
    • Filter to Event Types:
      • SMS Received
      • SMS Delivery Report Received
    • Endpoint Type: Web Hook
    • Endpoint: https://appsvc-eg-viewer.azurewebsites.net/api/updates
  8. Send an SMS to the ACS phone number.

Any log messages given by the failure

Expected/desired behavior

The above should generate an Event Grid message, but it will not.

OS and Version?

Windows 10 PRO

Versions

Mention any other details that might be useful

  • The problem is the default Github branch naming convention. Should be main, not master.
  • This caused me pain (my own fault!) so I'm guessing it causes others pain too

image


Thanks! We'll be in touch soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant