Improvements for setSecrets and unsetSecrets GraphQL endpoints

Hi there!

We’re working on an integration with you that involves updating Secrets for apps. We have one that works fine, but there are a couple issues we’re seeing.

First, since setSecrets doesn’t take the secrets provided as a complete set (i.e., if an existing secret isn’t passed in, it’s left alone), this requires a second mutation using unsetSecrets to remove any that shouldn’t exist. This results in one sync operation creating two releases in Fly. Is there any chance we might see another function in the future that could cover updating/removing secrets in one operation?

Second, there doesn’t appear to be a way to set a description for the release generated by these updates. It would be nice if we could use that to annotate why the release happened. If only one secret changes, it looks like there’s an automatic description added, but if multiple secrets are changed, no description is added.


Oh, and a couple other quick follow-ups questions:

  1. Do you have an API rate limit of any kind? If so, does it return a 429? Or does it return a 200 with an error extension? If the latter, what extension code is used for that error?

  2. Do you have a max number of secrets an app can have?

Our setSecrets mutation has a flag called replaceAll that should do it :slight_smile:

That’s definitely something we want too it’s just not on our roadmap yet.

So far we only have rate limiting on account creation/login so as long as you’re not creating bot accounts you’re fine :slight_smile:

No we do not

Hope these are helpful

1 Like

Thanks a ton! Completely missed that replaceAll option, hah! That’s exactly what I was after.

1 Like