Add test for app renaming #751
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Logs that are emitted by a renamed app are tagged with the new name without requiring a restart. - Check the origin of the emitted log as the cloud controller will emit logs against the new app name when the rename is performed. - Move recent logs function to the logs helper. cloudfoundry/diego-release#662 Co-authored-by: Andrew Crump <crumpan@vmware.com>
ctlong
approved these changes
Mar 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Are you submitting this PR against the develop branch?
Yes.
What is this change about?
The new test is dependent on PRs opened against Diego and CAPI which have not yet been merged. This PR should not be merged prior to release of the Diego and CAPI changes.
This is a breaking change as it requires those new versions of Diego and CAPI.
Please provide contextual information.
cloudfoundry/diego-release#662
What version of cf-deployment have you run this cf-acceptance-test change against?
None
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?
This is testing a common operator workflow.
How many more (or fewer) seconds of runtime will this change introduce to CATs?
45 seconds more.
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@ctlong