When using the secrets API, the API should not save to an OrgID that does not exist

[nisley]

Kept running into errors while trying to use Flux to retrieve secrets from the secret store.
influxdata/flux#1885

Turns out I sent in the wrong OrgID in:
http://localhost:9999/api/v2/orgs//secrets

I think I used my cloud orgId? At any rate - setting and getting secrets from the API worked flawlessly, but when I tried to use the secrets with secrets.get(), it failed because my session was of course in my org.

The API should not save secrets into an OrgID if that OrgID doesn't exist.

(As an aside, I imagine this could also lead to even more weirdness if by chance a new org is created and some secrets had already been stored in there? )

[imogenkinsman]

On the plus side, this is pretty much as OSS-specific bug. We have auth in place to ensure that the request is coming from someone with write permissions for that org, so this only affects users with global access to all orgs.

Should definitely be fixed though :)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.