Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
remote application on the offering side do not need status #7907
Conversation
anastasiamac
approved these changes
Oct 4, 2017
I think the code is ok but I have only basic understanding of the area :)
Since nothing uses it now, LGTM :D
|
$$merge$$ |
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
jujubot
merged commit 0870d37
into
juju:develop
Oct 4, 2017
1 check failed
continuous-integration/jenkins/pr-merge
This commit cannot be built
Details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
wallyworld commentedOct 4, 2017
Description of change
An early version of CMR created status for remote application proxies on the offering model.
This is not needed. Remove the status creation; nothing uses it.
QA steps
smoke test a basic cmr scenario