Skip to content
This repository was archived by the owner on Oct 22, 2024. It is now read-only.

Fix/remove validate lavamoat app UI from dev ci#605

Merged
cryptotavares merged 3 commits intomainfrom
fix/remove-validate-lavamoat-app-ui-from-dev-ci
May 24, 2023
Merged

Fix/remove validate lavamoat app UI from dev ci#605
cryptotavares merged 3 commits intomainfrom
fix/remove-validate-lavamoat-app-ui-from-dev-ci

Conversation

@cryptotavares
Copy link
Copy Markdown
Contributor

Overview

Currently, if we symlink the common workspace in the extension submodule, we will have a different policy file for the Desktop ui (not only for the Extension). This is due to the desktop popup. The solution is to recreate the desktop ui lavamoat policies on non-release CI executions and ignore the lavamoat validation step.

Changes

Root

  • lavamoat/ui/browserify/policy.json -> remove external references

Pipeline

  • .circleci/config.yml -> ignore lavamoat desktop ui validation on non release CI executions.
  • .circleci/config.yml -> regenerate the desktop ui lavamoat policies when we symlink the common workspace in the Extension dependencies

Common

None

App

None

@cryptotavares cryptotavares requested a review from a team May 17, 2023 16:27
@github-actions
Copy link
Copy Markdown

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@cryptotavares cryptotavares force-pushed the fix/remove-validate-lavamoat-app-ui-from-dev-ci branch 4 times, most recently from 71ec830 to 6a39958 Compare May 23, 2023 13:25
For non release CI execs
we want to run both the extension
as the desktop popup with the latest
version of the common package.
@cryptotavares cryptotavares force-pushed the fix/remove-validate-lavamoat-app-ui-from-dev-ci branch from 6a39958 to a7c6b58 Compare May 23, 2023 16:18
@cryptotavares cryptotavares merged commit 92fb331 into main May 24, 2023
@cryptotavares cryptotavares deleted the fix/remove-validate-lavamoat-app-ui-from-dev-ci branch May 24, 2023 09:42
@github-actions github-actions bot locked and limited conversation to collaborators May 24, 2023
yarn ${SCRIPT}

if git diff --exit-code -- ":(exclude)packages/app/submodules/extension"
if git diff --exit-code -- ":(exclude)packages/app/submodules/extension" ":(exclude)packages/app/lavamoat"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're skipping the validation in the case where we've regenerated the UI policies, then do we still need this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes you are correct, we don't... but it does not harm having it there.
We should eventually update the git diff to only consider the package.json path and not the entire repo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants