Integrate with Cloud

[olensmar]

As a user I would like to connect my local Monokle instance to my Monokle Cloud account, allowing me to use policies defined in Cloud for my projects locally. This includes the following "workflows":

• Authenticate with Cloud to establish a connection
• When working with a local repository I would like to select a corresponding Cloud project from which the policies would be used
  • If Monokle can auto-detect this connection that would be helpful
• Create Project from Cloud Project:
  • When I am authenticated with my cloud account I should be able to create a new local project for a corresponding Project/Repo defined in cloud - which would automatically clone the corresponding repo and set it up for Cloud policies

I no way should this Cloud Integration be "intrusive" or give me the impression that I have to have a Cloud account to use Monokle Desktop - this is purely optional

[julioramosest]

@olensmar some follow-up questions:

• The authentication with cloud is account-level, right? not at project level or even more granular
• How does that project "correspondence" work? is it set up manually? i.e. I'm in a desktop local project and I just select manually a cloud project I want to connect to? (obviously after connecting) This regardless of project titles, whatever?
• Do we sync up other characteristics aside of the policy? files/resources? no, right?
• In cloud is there also some visual reference that some project is connected to a desktop project?
• On creating project from cloud project: guess this would be a new option in the getting started cards, right?

[julioramosest]

UX and UI design (ongoing): https://www.figma.com/file/iDtnz4Gz9UF62acn4ccWOP/Cloud-integration?type=design&node-id=0%3A1&mode=design&t=6gamwssF5zLhTGxS-1

[olensmar]

thanks @julioramosest - answers:

• yes, authentication is with cloud account
• good question; the local project has to be for a repo in one of the cloud projects that the user has access to - perhaps the local project always has to be created from a corresponding cloud project/repo?! (as alluded to in the last question)
• no, just the policies
• no
• yes

@WitoDelnat @devcatalin please chime in to make sure I got this right..

[WitoDelnat]

Hi!

2. iirc then in the VSC Extension we rely on it being a git repository and then match it based on the git remote. There the idea is to be as low-config as possible as you generally don't start configuring VSC repo per repo.
3. Currently just policies, soon also suppressions; custom plugins & schemas

Remarks

• You can be part of multiple workspaces in which case you'd still need to select that as well (or we could flatten the list and select project could have a sub-description with the workspace it belongs to).

[julioramosest]

@olensmar @WitoDelnat @devcatalin please check design (posted above) and make your remarks.

Right Wito - let's go with a flat list, I'll add workspace to the details of the project

[julioramosest]

I added search/filter/sort-by capabilities to the project selection dropdowns - useful for busy accounts

[f1ames]

• Authenticate with Cloud to establish a connection

I guess it would be via device flow too? There are some GitHub login screens on the designs which are not needed in this case.

2. iirc then in the VSC Extension we rely on it being a git repository and then match it based on the git remote. There the idea is to be as low-config as possible as you generally don't start configuring VSC repo per repo.

Maybe we can have matching project (if there is one in a Cloud) as selected by default and then one can change if needed with dropdown?

Also, should we do https://github.com/kubeshop/monokle-core/issues/473 first (or in parallel) or duplicating this logic (auth related) will be fine for now (keep in mind we already have it duplicated in VSC and CLI)?

[WitoDelnat]

FYI, one remark is that suppressions will be linked from the project repository and not just the project so it might make sense that we already make this link explicit!