Update ENTSO-E parser to use new proxy

[madsnedergaard]

Description

Changes ENTSO-E parser to query via a new proxy service.

Double check

• I have tested my parser changes locally with poetry run test_parser "zone_key"

[github-actions]

PR Analysis

• 🎯 Main theme: Updating ENTSO-E parser to use a new proxy service
• 📝 PR summary: This PR updates the ENTSO-E parser to use a new proxy service. It simplifies the code by removing the need to shuffle and try multiple tokens, and instead uses a single token for the new proxy service. It also updates the script ENTSOE_capacity_update.py to reflect this change.
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: No
• ⏱️ Estimated effort to review [1-5]: 2, because the changes are straightforward and mainly involve updating URLs and removing redundant code.
• 🔒 Security concerns: No

PR Feedback

💡 General suggestions: The changes in this PR are clear and straightforward. However, it would be beneficial to add tests to ensure that the new proxy service works as expected. This could include tests to check the response from the new proxy service and handle any potential errors.

🤖 Code feedback:

---

relevant file	parsers/ENTSOE.py
suggestion	Consider handling the case where the get_token function returns None. Currently, if get_token returns None, it will be passed as a parameter to the session.get call, which may lead to unexpected behavior. [important]
relevant line	token = get_token("ENTSOE_TOKEN")

---

relevant file	scripts/ENTSOE_capacity_update.py
suggestion	Similar to the previous suggestion, consider handling the case where get_token returns None in this script as well. [important]
relevant line	token = args.api_token or get_token("ENTSOE_TOKEN")

---

✨ Usage tips:

---

To invoke the PR-Agent, add a comment using one of the following commands:

• /review: Request a review of your Pull Request.
• /describe: Update the PR title and description based on the contents of the PR.
• /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
• /ask <QUESTION>: Ask a question about the PR.
• /update_changelog: Update the changelog based on the PR's contents.
• /add_docs 💎: Generate docstring for new components introduced in the PR.
• /generate_labels 💎: Generate labels for the PR based on the PR's contents.
• /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To edit any configuration parameter from the configuration.toml, add --config_path=new_value.
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, add a /config comment.

[VIKTORVAV99]

Looks like it's working perfectly!

There was a reason the checklist had two boxes though 😉

[VIKTORVAV99]

Looks like it's working perfectly!

There was a reason the checklist had two boxes though 😉

[VIKTORVAV99]

Looks like we are mocking the tokens in a test too, we need to update that.

[madsnedergaard]

Looks like it's working perfectly!

There was a reason the checklist had two boxes though 😉

Haha, I've always just read the "pnpm ..." and assumed it was only about frontend 😅
Also thought we had pre-commit running for contrib, but seems like we never add ruff to the checks? What's missing from replacing isort and black completely there?

[VIKTORVAV99]

Looks like it's working perfectly!
There was a reason the checklist had two boxes though 😉

Haha, I've always just read the "pnpm ..." and assumed it was only about frontend 😅 Also thought we had pre-commit running for contrib, but seems like we never add ruff to the checks? What's missing from replacing isort and black completely there?

Pretty sure I uninstalled isort and black, I don't think we ever had all of them in there since they where so slow...

[madsnedergaard]

Looks like it's working perfectly!
There was a reason the checklist had two boxes though 😉

Haha, I've always just read the "pnpm ..." and assumed it was only about frontend 😅 Also thought we had pre-commit running for contrib, but seems like we never add ruff to the checks? What's missing from replacing isort and black completely there?

Pretty sure I uninstalled isort and black, I don't think we ever had all of them in there since they where so slow...

On the monorepo we still run isort and black on pre-commit, so maybe it's time to replace that :)

[VIKTORVAV99]

Looks like it's working perfectly!
There was a reason the checklist had two boxes though 😉

Haha, I've always just read the "pnpm ..." and assumed it was only about frontend 😅 Also thought we had pre-commit running for contrib, but seems like we never add ruff to the checks? What's missing from replacing isort and black completely there?

Pretty sure I uninstalled isort and black, I don't think we ever had all of them in there since they where so slow...

On the monorepo we still run isort and black on pre-commit, so maybe it's time to replace that :)

Yeah, I noticed we where still using black, led to some frustration when there was minor differences between ruff and black and I had autosave and format on save on and ruff as the default 😅.

But I can take care of the pre-commit hook in here, then we can start replacing things on the backend too.

[madsnedergaard]

Will merge and release this to production tomorrow so I can watch in case issues occur! :)