Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

manifest for azfunc-light fails to deploy due to bad TABLEENDPOINT env #578

Open

Description

I experienced an error while deploying this where it didn't generate the correct env variable in my .azure/url-prod/.env file (url-prod) being the env name of my az up.

(x) Failed: Deploying service azfunc-light

ERROR: error executing step command 'deploy --all': failed deploying service 'azfunc-light': failed executing template file: template: manifest template:35:27: executing "manifest template" at <.Env.FUNCSTORAGEA17CA_TABLEENDPOINT>: map has no entry for key "FUNCSTORAGEA17CA_TABLEENDPOINT"

To fix this I ended up:

Copying

URL_DATA_TABLEENDPOINT="https://urldatam5do5xihwalvo.table.core.windows.net/"

to a new entry of

FUNCSTORAGEA17CA_TABLEENDPOINT="https://urldatam5do5xihwalvo.table.core.windows.net/"

My guess is the env generation script needs adjusted?

Activity

  1. fboucher commented on Jun 22, 2025

    @fboucher
    Contributor

    maybe it's the "-" in the name?

    We should close this issues as we have no control over azd and there a workaround.

  2. B-Stewart commented on Jul 5, 2025

    @B-Stewart
    Author

    At that point I'd suggest then the hyphens get removed as the default names for these, it's not like I specified this name to break it, it's just the default so at the current time the default set up won't deploy correctly using the steps in README was my experience.

    var azFuncLight = builder.AddAzureFunctionsProject<Projects.Cloud5mins_ShortenerTools_FunctionsLight>("azfunc-light")

  3. added a commit that references this issue on Aug 31, 2025
  4. mstaelen commented on Aug 31, 2025

    @mstaelen
    Contributor

    I wrote this line
    output FUNCSTORAGEA17CA_TABLEENDPOINT string = funcstoragea17ca.outputs.tableEndpoint
    in /src/infra/main.bicep
    which allowed me to have a correct deployment.

  5. added a commit that references this issue on Oct 16, 2025
  6. fboucher commented on Jul 15, 2026

    @fboucher
    Contributor

    Chad Voelker (@ch-rob) please close this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions