[#346] Fix configs to support multi-tenancy

[roberlander2]

Description

This PR replaces the client_id field with an app_id field and an org_id field in all data models and existing database documents to support multi-tenancy. It also makes changes to the configs collection by merging it with the managed_group_configs collection and adding the model.Config wrapper around existing config models to better handle multi-tenancy.
Depends on rokwire/core-auth-library-go#86

Resolves #346
Resolves #224

Review Time Estimate

Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

• Immediately
• Within a week
• When possible

Type of changes

Please select a relevant option:

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Other (any another change that does not fall in one of the above categories.)

Checklist:

Please select all applicable options:

• I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
• I have updated the CHANGELOG.
• I have read the Contributor Guidelines.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My change requires updating the documentation.
• I have made necessary changes to the documentation.
• I have added tests related to my changes.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

---

[mdryankov]

Hi @shurwit & @roberlander2,

I'm getting compile issues:
Build Error: go build -o /Users/mladen/Projects/groups-building-block/__debug_bin -gcflags all=-N -l .

groups/core

core/administration.go:50:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess)
core/administration.go:66:20: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess)
core/administration.go:79:16: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess)
core/administration.go:111:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess)
core/administration.go:136:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) (exit status 1)

Also my understanding was that I could mainly comment and I have to wait for an explicit conformation by @shurwit before do any significiant review on my side. It looks that's not the case.

[mdryankov]

Minor version is not a good approach, because it obligates to upgrade version periodiaclly. When it's omittied it means to use the latest minor version during the build time.

I think it's better to use bullseye, unless there is a reason to use buster which I dont see.

What do you think?

[roberlander2]

Thanks for catching this @mdryankov, I will remove the minor version and make the change to bullseye. If I understand correctly, the reason to use bullseye over buster is because bullseye is the codename for the latest stable Debian release, so the buster release is now old.

Please let me know if I am missing anything with this explanation. Thanks!

[mdryankov]

Beautiful!

[roberlander2]

Hi @shurwit & @roberlander2,

I'm getting compile issues: Build Error: go build -o /Users/mladen/Projects/groups-building-block/__debug_bin -gcflags all=-N -l .

groups/core

core/administration.go:50:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) core/administration.go:66:20: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) core/administration.go:79:16: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) core/administration.go:111:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) core/administration.go:136:15: claims.CanAccess undefined (type *tokenauth.Claims has no field or method CanAccess) (exit status 1)

Also my understanding was that I could mainly comment and I have to wait for an explicit conformation by @shurwit before do any significiant review on my side. It looks that's not the case.

Thanks @mdryankov, these compile issues are due to this PR's dependence on rokwire/core-auth-library-go#86, which has not been added to a new version of the auth library yet. We plan to make this new release version soon. I will let you know when the new release has been integrated into this PR.

[mdryankov]

Let me know expplicitly when this one is good to go. Thanks!