Unable to set different values for different environments in resource configuration

Queries and Resources
,
1

  • Goal: Have different X-API-Key headers for the production and staging environments for an OpenAPI resource.

  • Steps:

  1. Create a new OpenAPI resource
  2. Add values in the Headers
  3. Add a staging environment
  4. Add values in the Headers for the staging environment
  5. Save changes
  6. Observe that values in the Headers for the production environment now match values for the staging environment

I used to be able to have different Header values when switching between production and staging environments for the OpenAPI resource, now the value are overriding each other.

Over half of our apps now work only in one environment...

2

This is still happening - exact same issue as this person had some time ago Issue with Endpoint Change When Switching Environments in Retool

3

Reproduction steps still remain the same.

4

Still happening.

Environment variables also cannot be used, because the OpenAPI resource does not allow curly braces in the values for Headers!

image
image1412×412 33.1 KB

5

I am also having this issue for x-api-key in my resources.

6

! was able to get around the issue using configuration variables. You can store different tokens for each environment there, and reference the configuration variable as the token value.

7

Thanks for reporting this!

@tomasvemola I was able to reproduce the bug you're showing in the screen recording, but the resource still works as expected in the app despite the incorrect resource set up (you can preview queries to see sanitized headers). Since I'm not seeing the issue persist in apps, I just wanted to double check that you are still seeing this issue persist within apps? Either way, definitely looks like a bug we should fix!

8

Yep this is happening to me too (just in case this wasn't more broadly known.)

9

Hi @Mentioum,

Thanks for chiming in. It's happening in apps and the resource configuration page?

Are you able to share screenshots?

10

Hi Tess,

I can confirm that the apps work correctly, even though the resource settings are not showing the correct values.

Although when using the OpenAPI resource, the headers do not seem to be sanitized (not when running, or previewing).

Staging headers

in-app staging
in-app staging1015×1240 71.6 KB

Production headers

in-app prod
in-app prod1016×1245 71.6 KB

In my resource settings, both environments are showing values for the production headers.

11

The issue isn't to do with the resulting activity from what I can see. I may be writing this in the wrong thread as this is happening for all REST API resources for me at the moment.

In the resource editing window (either via the query (in apps) or via the resources). There appears to be a rendering issue where fields are not updating correctly and/or are being replicated between environments.

I think screenshots will be more unhelpful as its hard to show... and i cant reproduce as its broken - I currently cant get the two environments to show different values for headers (even if I think they are saving correctly). I'm scared to check too much in case it breaks the resource.

Essentially editing the headers (and a few other things) in the production environment appears to edit them in the staging environment when switching between environments. The opposite is also true (staging -> production).

I appears that it 'SAVES' correctly so it works... but it shows the wrong thing in the UI consistently. I'm tentative about testing further.

1 Like
12

Yes, that's exactly what's happening on my side as well.

I actually did test it, and it seems exactly what you describe is happening.

1 Like
13

Thanks both! That's what I'm seeing too - it makes it super tricky to troubleshoot :disappointed:

@tomasvemola That looks correct for the headers by the way. We only sanitize certain headers, such as 'Authorization'

I'll follow up when I hear back from our engineering team

1 Like
14

Hey @Tess has there been any update on this? It's causing a bit of pain for our team.

1 Like
15

I don't have an update yet :disappointed: Will keep this thread posted

16

I'd like to suggest prioritising this if it hasn't already been fixed. Its kind of a big deal to not be able to see accurate values in resources.

It's not only extremely inconvenient but a massive security issue too to not be able to see what values you have set for different environments reliably.

17

This is a blocking issue for our team as well

18

This is a blocker for me as well @Tess.

19

I don't understand how this issue has been unresolved for three months. Utilizing APIs is one of the most fundamental and essential features for any app.

Everything was working fine until I made some changes last week, and now we need to choose between using Staging or Production. Naturally, we have to go with Production. However, this decision is hindering dozens of people from doing their jobs effectively, as many rely on Staging for testing and other tasks.

How is this not being addressed as a high-impact bug?

20

Hi @chrituri Thank you for chiming in! Our team is actively working on this :crossed_fingers: I hope to have an eta soon