Importing with --store-id leads to invalid state if store does not exist

[isaacharrisholt]

Running fga store import with the --store-id flag will result in an incorrect state if the store does not exist.

Essentially, it'll create the authorization_model record just fine, but the store_id column will be referencing a store that does not exist. Personally, my preferred behaviour in this case would be that the store is created, but the Go SDK doesn't currently support creating a store with a preset ID, as far as I can tell.

The reason for doing so would be to allow teams using shared environment variables to have a consistent setting for the store ID, as opposed to having to change it in local development every time a new store is created - this has become a bit of a pain for us at Documatic.

[aaguiarz]

Hi @isaacharrisholt

Can you describe your current workflow for local development?

We are discussing some options here to allow using a unique store name openfga/rfcs#27. You'd be able to configure SDKs/CLI to use the store name instead of the ID. The CLI/SDK will retrieve the store Id once and then use it. Do you think that would help?

Thanks a lot in advance

[isaacharrisholt]

Hey @aaguiarz, yes, a name would be fantastic! Would save us a lot of headaches.

In the meantime, I'd say the current behaviour is still a bug 😅

[rhamzeh]

@aaguiarz While the name would help - that's a separate issue.

The main issue here is:

• Writing Authorization Models to a non-existent store returns 201 openfga#690
• Enforce existence of the provided store_id in every API endpoint that requires one. openfga#714

[aaguiarz]

Yep, the behavior is a bug.

The way they'd prefer us to fix the bug is to use the store-id they send, but we'll be fixing by returning an error :). What they need is to have a predictable identifier for the store.