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

Setup: Configuring EventGrid namespace properties fails #59

Open
sseiber opened this issue Sep 7, 2023 · 2 comments
Open

Setup: Configuring EventGrid namespace properties fails #59

sseiber opened this issue Sep 7, 2023 · 2 comments

Comments

@sseiber
Copy link
Contributor

sseiber commented Sep 7, 2023

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

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

Minimal steps to reproduce

The Setup section asks the user to create/configure an EventGrid namespace. An Azure CLI command is given to set properties:

az resource create --id $res_id --is-full-object --properties '{
  "properties": {
    "isZoneRedundant": true,
    "topicsConfiguration": {
      "inputSchema": "CloudEventSchemaV1_0"
    },
    "topicSpacesConfiguration": {
      "state": "Enabled"
    }
  },
  "location": "westus2"
}'

However, in the current version of EventGrid there is an MQTT option, which when enabled, will set these properties to the desired value (see pic):
image

Without enabling the MQTT option these properties are read-only and the command will fail when trying to set them.

Expected/desired behavior

The documentation should be updated to instruct the user to enable the "MQTT" feature.


Thanks! We'll be in touch soon.

@rido-min
Copy link
Contributor

rido-min commented Sep 8, 2023

I've deployed a new EG instance with the provided script, and the EG resource was created with the correct configuration and no issues.

Did you create the resource from the portal and tried to configure with the script?

@rido-min
Copy link
Contributor

talked to @sseiber offline

He was confused with the section title, as he thought the instance should be created in the portal and then configured.

An easy fix will be to rename the configure-event-grid-namespace section in Setup.md to create-and-configure-event-grid-namespace

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

2 participants