Update Dockerhub Repository and Delete Config Session Variable

[skarious]

Update Dockerhub Repository and Delete Config Session Variable

Summary by Sourcery

Update the Docker swarm configuration for the evolution_api_v2 service to use the new Docker Hub repository and tag, and remove an obsolete session version environment variable.

Enhancements:

• Bump the evolution_api_v2 container image to evoapicloud/evolution-api:v2.3.0

Deployment:

• Remove the deprecated CONFIG_SESSION_PHONE_VERSION environment variable from the service definition and example

[sourcery-ai]

Reviewer's Guide

This PR updates the Docker Swarm configuration to point to the new DockerHub repository and version for the evolution-api service, and removes an outdated session configuration variable from the environment settings.

Class diagram for environment variable changes in evolution-api service

classDiagram
  class EvolutionApiService {
    +CONFIG_SESSION_PHONE_CLIENT: string
    +CONFIG_SESSION_PHONE_NAME: string
    -CONFIG_SESSION_PHONE_VERSION: string
    +QRCODE_LIMIT: int
    +OPENAI_ENABLED: bool
    +DIFY_ENABLED: bool
    ...
  }

Loading

File-Level Changes

Change	Details	Files
Updated Docker image reference to new repository and version	Replaced image atendai/evolution-api:v2.1.2 with evoapicloud/evolution-api:v2.3.0	Docker/swarm/evolution_api_v2.yaml
Removed obsolete session environment variable	Deleted CONFIG_SESSION_PHONE_VERSION entry	Docker/swarm/evolution_api_v2.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @skarious - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[KokeroO]

Realmente o hub está errado.

Em relação a versão do WhatsApp eu ainda acho necessário setar o valor de CONFIG_SESSION_PHONE_VERSION nela em produção. Muitas mudanças na meta causam problemas no qual o script da Evolution ainda não está preparado.
Na minha opinião é algo que ainda não se pode abandonar em produção.

[dpaes]

@skarious nunca aponte para a main, sempre pra develop e complementando com o @KokeroO, não pode retirar essa variavel de ambiente, pois essa responsabilidade não pode ficar do lado apenas da baileys definir a versão do whatsapp web, pois pode ter casos em que ela não vai sanar o problema. Se puder ajustar