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

Fix stack being over-ridden everytime in v7 push #2148

Merged
merged 1 commit into from
Mar 4, 2021

Conversation

tstannard
Copy link

Does this PR modify CLI v6 or v7?

v7

Description of the Change

When v7 push is called with a manifest that has a stack field set, the cf CLI would override that field to an empty string. This PR makes it so that we only override the stack field in the manifest when a user provides a stack with the -s flag.

Why Is This PR Valuable?

When users set the stack field in their manifest, they would like to use it.

Why Should This Be In Core?

Bug fix.

Applicable Issues

cloudfoundry/cloud_controller_ng#1819

How Urgent Is The Change?

We would like this shipped in the next minor v7 release

Other Relevant Parties

@amhuber who reported this issue

Whenever an app was pushed in v7 if the manifest had a stack field in
it, it would be always overriden by the cf CLI with whatever you put in
for -s on cf push, even if you did not submit this flag.  Thus leading
to stack always being an empty string in those situations.

Co-authored-by: Jenna Goldstrich <jgoldstrich@pivotal.io>
Co-authored-by: Teal Stannard <tstannard@pivotal.io>
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 22, 2021

CLA Signed

The committers are authorized under a signed CLA.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/177048452

The labels on this github issue will be updated when the story is started.

Copy link
Member

@a-b a-b left a comment

Choose a reason for hiding this comment

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

LGTM

@a-b
Copy link
Member

a-b commented Mar 4, 2021

@thausler786 can you please review the proposed change from the product perspective?

@thausler786
Copy link

This is a change in behavior we will have to call out in the release notes.

Reading the command I believe the user would clearly expect that the CLI would use the stack in the manifest as given, so this is a straightforward bug fix that should be included, even if it does cause a change in behavior.

@a-b a-b merged commit f3e9e21 into v7 Mar 4, 2021
@a-b
Copy link
Member

a-b commented Mar 4, 2021

cc @reedr3

@moleske moleske deleted the fix-stack-field-being-overriden-everytime branch August 24, 2023 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants