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

Pass mountPaths.appDirName to lifecycle as -app arg #1146

Closed
wants to merge 4 commits into from

Conversation

jkutner
Copy link
Member

@jkutner jkutner commented Apr 28, 2021

Summary

Fast follow fix for #1141

Output

Before

app dir was mounted, but lifecycle was not cd-ing into it.

After

The provide workspace becomes the CNB_APP_DIR

Documentation

  • Should this change be documented?
    • Yes, see #___
    • No

@jkutner jkutner requested a review from a team as a code owner April 28, 2021 16:17
@github-actions github-actions bot added the type/enhancement Issue that requests a new feature or improvement. label Apr 28, 2021
Copy link
Member

@dfreilich dfreilich left a comment

Choose a reason for hiding this comment

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

I should've thought of this when I merged in the other PR. Good catch!

@@ -193,7 +193,7 @@ func (l *LifecycleExecution) Create(ctx context.Context, publish bool, dockerHos

opts := []PhaseConfigProviderOperation{
WithFlags(l.withLogLevel(flags...)...),
WithArgs(repoName),
WithArgs("-app", l.mountPaths.appDirName(), repoName),
Copy link
Member

Choose a reason for hiding this comment

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

Does lifecycle expect it in the format \appdir, or in c:\appdir? If the later, we can use mountPaths.appDir() instead

Copy link
Member Author

@jkutner jkutner Apr 28, 2021

Choose a reason for hiding this comment

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

oh, i might need to revert 51887a3 in favor of using mountPaths.appDir()

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed in 9cc6613

@codecov
Copy link

codecov bot commented Apr 28, 2021

Codecov Report

Merging #1146 (3104129) into main (5d39613) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1146   +/-   ##
=======================================
  Coverage   80.80%   80.80%           
=======================================
  Files         136      136           
  Lines        8299     8299           
=======================================
  Hits         6705     6705           
  Misses       1164     1164           
  Partials      430      430           
Flag Coverage Δ
os_linux 80.29% <100.00%> (+0.04%) ⬆️
os_macos 77.82% <100.00%> (+0.04%) ⬆️
os_windows 80.71% <100.00%> (ø)
unit 80.29% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@jkutner jkutner requested review from a team and dfreilich April 29, 2021 02:28
@dfreilich
Copy link
Member

Closing this in favor of #1149

@dfreilich dfreilich closed this Apr 29, 2021
@jromero jromero deleted the jkutner/fix-1121-bug branch July 21, 2021 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants