Fakenamedeployment is not removed by modelname for Azure

[AndyMik90]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.5.11

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

When adding Azure models locally, it does not use the model name as the label, as it does on cloud instances.

it only says "fake-deployment-name-label". Added in the same way on both local source and on cloud. Cloud works, not local.

✔️ Expected Behavior

Model name is set as the label

❌ Actual Behavior

fake-deployment-name-label is set regardless of the modelname.

[dosubot[bot]]

Hey @AndyMik90, great to see you back! Hope everything else has been smooth since our last chat.

Thank you for providing a detailed description of the issue you're facing. Based on the context provided, it seems there is indeed a difference in the codebase that handles the labeling of deployments between the cloud and self-hosted environments. This difference is likely due to the distinct functionalities and configurations required for each deployment type, as outlined in the environments.md document.

However, I wasn't able to find specific information within the repository regarding the code segment that handles the labeling of deployments in the self-hosted environment, a configuration setting that controls the labeling of deployments, or a bug that could be causing the "fake-deployment-name-label" to be assigned instead of the actual model name. Similarly, I couldn't find any information about a difference in the way the Dify codebase handles the labeling of deployments for Azure models compared to other models.

Given this, it's possible that the issue you're experiencing is due to a bug or an undocumented feature in the Dify codebase. It would be helpful if you could provide more information about your setup, such as the specific steps you took to add the Azure models to your self-hosted Dify setup, and any error messages or logs you might have encountered during the process. This additional information could help us pinpoint the cause of the issue and suggest a potential solution.

Sources

• en/getting-started/install-self-hosted/environments.md

#### About Dosu

This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.

[Yeuoly]

how did you add the model? as usual, label should be the same as the model's name

[dosubot[bot]]

Hi, @AndyMik90

I'm helping the Dify team manage their backlog and am marking this issue as stale. It looks like you reported an issue where the label for Azure models added locally does not use the model name as expected, instead using "fake-deployment-name-label". There have been some comments from dosubot and Yeuoly, with dosubot acknowledging the difference in labeling between cloud and self-hosted environments and requesting more information about the setup and any encountered error messages. Yeuoly also inquired about the method used to add the model, noting that the label should typically match the model's name.

Could you please confirm if this issue is still relevant to the latest version of the Dify repository? If it is, please let the Dify team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days. Thank you!