Skip to content

Conversation

@killthekitten
Copy link
Contributor

@killthekitten killthekitten commented May 21, 2024

What

This patch makes the api_key parameter of the Qonto source required and marks it as a secret

How

The manifest.yaml has been changed accordingly

Review guide

I haven't tested the changes locally. I'd appreciate if someone else could do this during a review:

  1. Run the tests locally
  2. Set up the source
  3. Check that the contents of the API key field are hidden behind the asterisks

User Impact

We saw that the update from 0.1.0 to 0.2.0 dropped the API key and we had to re-add it. Would this require re-adding the API key again since it is now a secret?

Also, can we ask for a version bump consent in the UI?

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌
@vercel
Copy link

vercel bot commented May 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
airbyte-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2024 5:06pm
Copy link
Contributor

@marcosmarxm marcosmarxm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcosmarxm
Copy link
Contributor

Hello 👋 , your feedback matters a lot to us. Can you spare just 3 minutes to complete a survey? We're dedicated to making the contributor experience even better, and your input is key to achieving excellence. Thank you for helping us improve!

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

Labels

area/connectors Connector related issues area/documentation Improvements or additions to documentation community connectors/source/qonto

3 participants