Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove legacy CLI image #1798

Merged
merged 4 commits into from
May 7, 2020
Merged

Remove legacy CLI image #1798

merged 4 commits into from
May 7, 2020

Conversation

smlx
Copy link
Member

@smlx smlx commented Apr 16, 2020

Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for changelog and subsystem label(s) applied

This image is no longer in use by amazee.io, having been superseded by https://github.com/amazeeio/lagoon-cli

Closing issues

n/a

This functionality has been superseded by
https://github.com/amazeeio/lagoon-cli
@smlx smlx added the 2-build-deploy Build & Deploy subsystem label Apr 16, 2020
@smlx smlx requested a review from Schnitzel April 16, 2020 10:17
Copy link
Member

@rocketeerbkw rocketeerbkw left a comment

Choose a reason for hiding this comment

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

Some more stragglers (found by regex search cli\b):

Also, did you just rm the cli folder? I wonder if we should also explicitly remove the node packages and clean up the shared yarn workspace node_modules folder. Some quick googling comes up blank with the correct way to "yarn delete workspace" though. Not sure if it's worth it to cd cli && yarn remove <list> < every> <package> <here> before deleting the cli directory. It might also be possible to just run yarn install with the cli folder gone?

@smlx
Copy link
Member Author

smlx commented Apr 17, 2020

Some more stragglers (found by regex search cli\b)

Ah thanks! I'll remove those..

Also, did you just rm the cli folder?

Yes...

I wonder if we should also explicitly remove the node packages and clean up the shared yarn workspace node_modules folder. Some quick googling comes up blank with the correct way to "yarn delete workspace" though. Not sure if it's worth it to cd cli && yarn remove < every> before deleting the cli directory. It might also be possible to just run yarn install with the cli folder gone?

This is not an ecosystem I'm familiar with.. happy to take any expert advice.

Will yarn remove cli before deleting the directory work to update the workspace?

@rocketeerbkw
Copy link
Member

I'm no expert but I found a support channel in the yarn discord.

If you run yarn (with no arguments) in the root folder of the repo, it should detect that the cli workspace is gone and update the yarn.lock accordingly. I'd expect a diff of that file to show a bunch of package versions being removed.

yarn remove cli doesn't work because cli isn't an actual package

docker run \
  --rm \
  --entrypoint /usr/local/bin/yarn \
  -w /mnt/lagoon \
  -it \
  --volume $PWD:/mnt/lagoon \
  node:dubnium-jessie \
  install
@smlx
Copy link
Member Author

smlx commented Apr 21, 2020

Yarn seemed to run correctly, 🤞 for CI

@smlx smlx requested a review from rocketeerbkw April 21, 2020 11:51
Copy link
Member

@rocketeerbkw rocketeerbkw left a comment

Choose a reason for hiding this comment

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

Awesome!

@Schnitzel Schnitzel merged commit 0f99854 into master May 7, 2020
@smlx smlx deleted the remove-cli branch May 8, 2020 09:34
@rocketeerbkw rocketeerbkw mentioned this pull request Aug 4, 2022
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-build-deploy Build & Deploy subsystem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants