-
Notifications
You must be signed in to change notification settings - Fork 43
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
[MNOE-1287] Delisted apps #785
base: 4.0
Are you sure you want to change the base?
Conversation
cc5dcdf
to
b0a71a3
Compare
Update tenant config schema to include only active apps
b0a71a3
to
8eca0d0
Compare
@ouranos Rebased on 4.0 |
@@ -156,9 +156,9 @@ def self.update_locales_list! | |||
# Populate the app list after fetching it from MnoHub | |||
# TODO: replace with a Proc.call | |||
def self.update_application_list! | |||
available_app_nids = App.all.map(&:nid) | |||
available_app_nids = App.where(active: true).map(&:nid) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a default scope to App?
I don't think mnoe should ever see inactive apps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or it could be done on the hub side
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, maybe best to add it as a filter at the resource level in hub?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, should be by default I reckon?
The inactive apps shouldn't be exposed on the API. We only need them in the DevPlatformSync job to re-enable them if they get re-activated from the DevPlatform
8eca0d0
to
c6b40f8
Compare
c6b40f8
to
d266abc
Compare
Add temp workaround for travis bundler issue. To be removed once issue has been resolved.
@ouranos Updated specs, looks like they were failing due to updates in nokogiri or sanitize gems. Build was then failing due to bundler failures in travis caused by outdated rubygems. I've added a temp fix for this until it is fixed in travis (added |
Update tenant config schema to include only active apps